Just checking, do you have your "ShorexTour"
EJB named in the same ejb-jar.xml!
Yes, the entity EJB is named "ShorexTour" in the deployment descriptor.
I just wrote a test class that connects to the JNDI naming service from another JVM process. It successfully looked up the session facade and called it's methods. But when I tried to look up the local interface of the entity EJB, I got a naming exception. Which is good and what I was hoping would happen.
My guess is that JBoss will not allow the lookup of the local interface from the outside. Just wondering how it knows.
I have made conclusions which poin to the same direction, listing Context.list("java:/comp/env") succeeds only in a servlet, when I try it from a java-client I get javax.naming.NameNotFoundException: comp not bound
Yes, java:comp/env is an internal representation. You cannot reference it from outside unless you have a client descriptor that resolves java:comp/env to java:/JNDIName(or whatever ur jndi is).
Im not sure how much of a progress is made on the client side descriptors in j2ee1.4 but it sure was in earlier releases.