Java Reference
In-Depth Information
Element
Description
bean-name
This is the bean's class name
fully-qualified-classname-of-the-remote-
interface
This is the fully qualified class name of the remote interface
So the corresponding JNDI binding for your
TheatreInfo EJB
, packaged into a file
named
ticket-agency-ejb.jar
, will be:
ejb:/ticket-agency-ejb//TheatreInfo!
com.packtpub.wflydevelopment.chapter3.boundary.TheatreInfoRemote
On the other hand, stateful EJBs will contain one more attribute,
?stateful
, at the bot-
tom of the JNDI string; this will result in the following JNDI naming structure:
ejb:<app-name>/<module-name>/<distinct-name>/
<bean-name>!<fully-qualified-classname-of-the-remote-interface>?stateful
Also, here's the corresponding binding for the
TheatreBooker
class:
ejb:/ticket-agency-ejb//TheatreBooker!
com.packtpub.wflydevelopment.chapter3.boundary.TheatreBookerRemote?stateful
Note
If you pay attention to the server logs, you will see that once your application is deployed,
a set of JNDI bindings will be displayed on the server console. For example:
java:global/ticket-agency-ejb/
TheatreInfo!com.packtpub.wflydevelopment.chapter3.boundary.TheatreInfoRemote
java:app/ticket-agency-ejb/
TheatreInfo!com.packtpub.wflydevelopment.chapter3.boundary.TheatreInfoRemote
java:module/
TheatreInfo!com.packtpub.wflydevelopment.chapter3.boundary.TheatreInfoRemote
java:jboss/exported/ticket-agency-ejb/
TheatreInfo!com.packtpub.wflydevelopment.chapter3.boundary.TheatreInfoRemote
