EJB Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
An EJB Client Context may contain any number of [[#EJB_Receivers|EJB receivers]]. | An EJB Client Context may contain any number of [[#EJB_Receivers|EJB receivers]]. | ||
There can potentially be more than one EJB Client Contexts into a JVM. | |||
==EJB Receiver== | ==EJB Receiver== | ||
An EJB receiver is a component that knows how to communicate with a server that is capable of handling EJB invocations. | An EJB receiver is a component that knows how to communicate with a server that is capable of handling EJB invocations. | ||
Revision as of 17:00, 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.
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.