|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (9)
View Page HistoryWhen a JBI message is received on an endpoint linked to an EJB, the message is transformed into a RMI message, then sent to the linked EJB.
\\
!petals-bc-ejb.png!
\\
The RMI message is created following these steps :
# The JBI message payload is mapped to Java objects. These objects (and their types) are used as operation parameters for the RMI call. The mapping is done thanks to the PEtALS-JAXB-Databinding library. For more information about XML databinding feel free to read the chapter entitled XML to Java binding.
# The JBI message payload is mapped to Java objects. These objects (and their types) are used as operation parameters for the RMI call. The mapping is done thanks to the PEtALS-JAXB-Databinding library. For more information about XML databinding feel free to read the chapter entitled XML to Java binding.
{info}
For more information about JAAS read the chapter : JAAS authentication for EJB calls{info}
In order to reach the remote EJB, the component need to get an RMI stub of the EJB from a JNDI server. The JNDI name
of the target EJB is defined in the parameter ejb.jndi.name.
of the target EJB is defined in the parameter ejb.jndi.name.
{info}
In order to reach the remote EJB, the component need to get an RMI stub of the EJB from a JNDI server. The JNDI name of the target EJB is defined in the parameter ejb.jndi.name.
In order to reach the remote EJB, the component need to get an RMI stub of the EJB from a JNDI server. The JNDI name of the target EJB is defined in the parameter ejb.jndi.name.
The external EJB is called and the response is processed by the PEtALS-JAXB-Databinding library and then returned to the JBI environment.