Revision as of 17:03, 23 March 2017

Internal

An EJB remote application can be one of the following:

a standalone Java application
another component that runs within a application server instance, and makes invocations into remote EJBs. In this case, each deployed application will have its own EJB client context, and the application's components will share the EJB client context.

JBoss EAP 6 introduced the EJB client API for managing remote EJB invocations. The EJB client API uses the EJB Client Context.

The EJB Client Context may be associated with, and used by more than one thread concurrently.

The EJB Client Context is configured with jboss-ejb-client.properties for standalone applications and with jboss-ejb-client.xml for applications deployed within the EAP. Each deployed application will have its own EJB Client Context.

An EJB Client Context may contain any number of EJB receivers.

There can potentially be more than one EJB Client Contexts into a JVM.

An EJB receiver is a component that knows how to communicate with a server that is capable of handling EJB invocations.

@@ Line 17: / Line 17: @@
 The EJB Client Context may be associated with, and used by more than one thread concurrently.
-The EJB Client Context is configured with [[Jboss-ejb-client.properties#Overview|jboss-ejb-client.properties]] for [[#standalone_ejb_client|standalone applications]] and with [[Jboss-ejb-client.xml#Overview|jboss-ejb-client.xml]] for applications deployed within the EAP. Each deployed application will have its own EJB Client Context.
+The EJB Client Context is configured with [[Jboss-ejb-client.properties#Overview|jboss-ejb-client.properties]] for [[#standalone_ejb_client|standalone applications]] and with [[Jboss-ejb-client.xml#Overview|jboss-ejb-client.xml]] for applications deployed within the EAP. Each [[#deployed_application|deployed application]] will have its own EJB Client Context.
 An EJB Client Context may contain any number of [[#EJB_Receivers|EJB receivers]].