EJB implementation

Question

Hi,
I am calling an EJB from a normal java class by lookup. If I do a plain Lookup with the JNDI name it goes pretty fine and I am able to get the EJBObject instance. but If i try to call with the reference i mean creating reference which we create when we are calling one EJB from the other or when we call and EJB from a web layer it is giving namenotfound exception. Can anybody let me know whether we can call the ejb from a normal java class with a reference when both the ejb and the java class are in the same package.
Below give is the code which demonstrates my problem.
code:
//          Context jndiContext = new InitialContext();          Object obj = jndiContext.lookup("java:comp/env/ejb/Test");          TestHome testHome = (TestHome)PortableRemoteObject.narrow(obj,TestHome.class);          Test test = testHome.create();          test.processTransaction(100);
Cheers,
Naidu Sanapala
Laurel, Maryland, USA.
Naidu Sanapala - JAVA ARCHITECT , Laurel , Maryland , USA
1.SUN Certified Enterprise Architect for J2EE Technology
2.Sun Certified [EJB] Business Component Developer for the J2EE Platform
3.Sun Certified Web Component Developer for the J2EE Platform
4.Sun Certified Java Programmer for the Java 2 Platform - 1.4
5.IBM Certified Solution Developer for XML and Related Technologies
....................................................................................................

Answer 1

Hi Naidu,
It's not a question of whether the calling code and the target ejb are in the same java package. What matters is whether the calling code is part of a J2EE component and where it is executing. Any code running within a J2EE component (servlet, jsp, ejb, Application Client) can declare component dependencies and look them up via java:comp/env. In J2EE 1.4 and earlier this means declaring the dependency in web.xml, ejb-jar.xml or application-client.xml.
If you have code running outside of an Application Server and outside of an Application Client container, it's not a J2EE component and therefore cannot use the J2EE component namespace (java:comp/env). Technically these kinds of applications are not portable. However, most implementations support them by requiring that the code do a direct global lookup of a JNDI name.
--ken