Can not lookup EJB2 from other EJB2, but can do it from servlet?

Each EJB has its own java:comp namespace, so in J2EE 1.4, each entity or message-driven must have its own ejb-ref (or ejb-local-ref ) In JavaEE 6, a single EJB (or the servlet), can declare an ejb-ref with a java:module (or java:app ) prefix to allow any component in that scope to be able to share the reference.

Each EJB has its own java:comp namespace, so in J2EE 1.4, each or must have its own (or ). In JavaEE 6, a single EJB (or the servlet), can declare an ejb-ref with a java:module (or java:app) prefix to allow any component in that scope to be able to share the reference.

Thanks for your answer. But it doesn't work for me. I tried to do this: TransportBean ejb/Transport ejb/Task java:comp/env/ejb/Task And got these errors: WARNING: This bean TransportBean has no ejb reference by the name of ejb/Task SEVERE: DPL8006: get/add descriptor failure : ejb-ref TO ejb/Task SEVERE: DPL8007: Invalid Deployment Descriptors element jndi-name value java:comp/env/ejb/Task – grapescan May 17 at 5:18 Where did the and elements come from?

Those aren't valid for ejb-jar. Xml (or web. Xml).

– bkail May 17 at 15:29 These elements are created by NetBeans GUI editor in file sun-ejb-jar. Xml (now glassfish-ejb-jar. Xml).

After your reply I realised that must be placed in ejb-jar.xml. It was not obvious becuse NetBeans GUI editor (again! ) for ejb-jar.

Xml has no option to do that. Now lookup works great. Thanks for your help!

– grapescan May 17 at 19:56 Ah, that explains it. Glad you were able to get it working. – bkail May 17 at 21:30.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.