The EJB mediator calls an external Enterprise JavaBean(EJB) and stores the result in the message payload or in a message context property. Currently, this mediator supports EJB3 Stateless Session Beans and Stateful Session Beans.
The EJB mediator is a content-aware mediator.
|Beanstalk ID||Reference to the application server specific connection source information, which is defined at the synapse.properties.|
|Class||This required the remote interface definition provided in the EJB 3.0 (EJB service invocation remote/home interface).|
When the EJB context is invoked in the form state-full bean then the related ejb session status specified will be stored in here. Possible values are as follows.
This parameter specifies whether the Enterprise Entity Manager should remove the EJB context related parameters once the state full/stateless session is invoked.
If a particular EJB method returns, then the return object can be saved against the the name provided in the target at the synapse property context.
The Java Naming and Directory Interface (JNDI) is an application programming interface (API) for accessing different kinds of naming and directory services. JNDI is not specific to a particular naming or directory service. It can be used to access many different kinds of systems including file systems; distributed objects systems such as CORBA, Java RMI, and EJB; and directory services such as LDAP, Novell NetWare, and NIS+.
|Add Argument||Can be used to define the arguments which is required for the particular ejb method to be invoked Expression/Value.|
You can click the "Namespaces" link to add namespaces if you are providing an expression. You will be provided another panel named "Namespace Editor" where you can provide any number of namespace prefixes and the URL used in the XPath expression.
In this example, the EJB Mediator does the EJB service invocation by calling getStoreById pubished at the application server and exposed via
then response will be assigned to the target specified (variable/expression).