Glassfish ACC（应用程序客户端容器）的记录 [英] documention for the Glassfish ACC (Application Client Container)
问题描述
我发现这个有关ACC（应用程序客户端容器）的信息：
I found this bit of information about the ACC (Application Client Container):
ACC使用IIOP ORB联系服务器在注射期间。 ORB的
默认端口为3700. Java Web Start支持
自动将ORB相关属性设置为指向正确的
ORB地址。如果您正在运行群集，那么这包括所有
当前活动的群集成员的ORB。
The ACC uses the IIOP ORB to contact the server during injection. The default port for the ORB is 3700. The Java Web Start support automatically sets the ORB-related properties to point to the correct ORB address. If you are running a cluster then this includes all currently-active cluster members' ORBs.
https://www.java.net/node/679235
然而，这个记录一般来说似乎很轻。虽然在开发指南中提到：
However, the documention, in general, seems light. While it is mentioned in the Development Guide:
介绍应用程序客户端容器
Introducing the Application Client Container
应用程序客户端容器（ACC）包括一组Java类，
库和其他需要并分发给
的其他文件，在其自己的Java虚拟机中执行的Java客户端程序
（JVM）。 ACC管理Java EE应用程序客户端
组件（应用程序客户机）的执行，用于访问各种
的Java EE服务（如JMS资源，EJB组件，web
服务，安全性等等）从Oracle
GlassFish Server之外的JVM。 ACC使用
RMI-IIOP协议与GlassFish服务器进行通信，并使用与其捆绑的客户端ORB来管理RMI-IIOP通信
的详细信息。与其他Java
EE容器相比，ACC是轻量级的。有关调试
应用程序客户端的信息，请参阅应用程序客户端调试。
The Application Client Container (ACC) includes a set of Java classes, libraries, and other files that are required for and distributed with Java client programs that execute in their own Java Virtual Machine (JVM). The ACC manages the execution of Java EE application client components (application clients), which are used to access a variety of Java EE services (such as JMS resources, EJB components, web services, security, and so on.) from a JVM outside the Oracle GlassFish Server. The ACC communicates with the GlassFish Server using RMI-IIOP protocol and manages the details of RMI-IIOP communication using the client ORB that is bundled with it. Compared to other Java EE containers, the ACC is lightweight. For information about debugging application clients, see Application Client Debugging.
GlassFish Server开源版应用程序开发指南4.0版
GlassFish Server Open Source Edition Application Development Guide Release 4.0
还有：
应用程序客户端容器
The Application Client Container.
尽管使用JNDI从客户端访问EJB比在
EJB 2.x中更简单，但仍然相当尴尬。好消息是，如果客户端从
应用程序客户端容器（ACC）中运行，我们可以
完全免除JNDI。 EJB 3规范不是
要求符合EJB的应用程序服务器提供ACC，而
使其包含可选。因此，并不是所有EJB兼容的
应用程序服务器都提供了一个ACC，但GlassFish却是这样。
Although accessing an EJB from a client using JNDI is simpler than in EJB 2.x, it is still rather awkward. The good news is that we can dispense with JNDI altogether if the client runs from within an application client container (ACC). The EJB 3 specification does not mandate that an EJB-compliant application server provides an ACC but makes its inclusion optional. Consequently not all EJB-compliant application servers provide an ACC, however GlassFish does.
http://www.developer.am/ejb3/?page=application-client-container
更多的是一般的描述。没有关于ACC及其使用的官方文档？
it's more of a general description. There's no official documentation on the ACC and its usage specifically?
推荐答案
应用程序开发指南包含一些部分（仅提供PDF格式） ）：
The Application Development Guide contains some sections (only available as PDF?):
https://glassfish.java.net/docs/4.0/application-development-guide.pdf
https://glassfish.java.net/documentation.html
这篇关于Glassfish ACC（应用程序客户端容器）的记录的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
