There is a @ejb.util task that has a generate attribute that can be set to logical or physical. This changes the initial context lookup from a java:comp/env constant to a jndi constant that is defined in the beans' home interface.
I deploy using the logical which is the default. and the {ejb-name}Util.getHome() method throws an exception "ejb not bound". If I use physical I can create the bean fine.
I am using junit test which will need to use the jndi version because they will normally be executed from boxes other that the jboss server. I also have servlet's/jsp's that are being deployed to the jboss server 3.2.1 using jetty. What is the best method for servlets on the same jvm to connect to the ejbs.
My question is when is it a good time to use java:/comp/env syntax, what is the purpose of the comp name and what role do local interfaces verses remote interfaces play?
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
