EJB Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
An EJB remote application can be one of the following: | An EJB remote application can be one of the following: | ||
* <span id="standalone_ejb_client"></span>a standalone Java application | * <span id="standalone_ejb_client"></span>a standalone Java application | ||
* another component that runs within a application server instance, and makes invocations into remote EJBs. | * 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|EJB client context]], and the application's components will share the EJB client context. | ||
=EJB Client API= | =EJB Client API= | ||
Revision as of 17:01, 23 March 2017
Internal
EJB Remote Applications
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.
EJB Client API
JBoss EAP 6 introduced the EJB client API for managing remote EJB invocations. The EJB client API uses the EJB Client Context.
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.
An EJB Client Context may contain any number of EJB receivers.
There can potentially be more than one EJB Client Contexts into a JVM.
EJB Receiver
An EJB receiver is a component that knows how to communicate with a server that is capable of handling EJB invocations.