@EJB(lookup) fails while context.lookup() is successfull

[lmcdasi]

I have a war file that has an EJB. @EJB(lookup="java:global/test-war/LcExample!<mypkg>.example.api.ILcExample") fails to do the injection while initialContext.lookup("java:global/test-war/LcExample!<mypkg>.example.api.ILcExample") returns the ejb object.

I am wondering what do I do wrong or how it is suppose to work by using @EJB. The war content is :

    0 Thu Oct 20 10:10:48 EDT 2011 META-INF/

   126 Thu Oct 20 10:10:46 EDT 2011 META-INF/MANIFEST.MF

     0 Thu Oct 20 10:10:48 EDT 2011 WEB-INF/

     0 Thu Oct 20 10:10:48 EDT 2011 WEB-INF/classes/

     0 Thu Oct 20 10:10:48 EDT 2011 WEB-INF/classes/com/

     0 Thu Oct 20 10:10:48 EDT 2011 WEB-INF/classes/com/.../

     0 Thu Oct 20 10:10:48 EDT 2011 WEB-INF/lib/

     0 Thu Oct 20 10:10:48 EDT 2011 css/

     0 Thu Oct 20 10:10:48 EDT 2011 docs/

     0 Thu Oct 20 10:10:48 EDT 2011 images/

   448 Thu Oct 20 10:01:02 EDT 2011 WEB-INF/jboss-web.xml

  1297 Thu Oct 20 09:44:42 EDT 2011 WEB-INF/web.xml

  6756 Thu Oct 20 10:10:46 EDT 2011 WEB-INF/classes/com/.../FmHandler.class

  2528 Thu Oct 20 10:10:46 EDT 2011 WEB-INF/classes/com/.../CmListener.class

  5730 Thu Oct 20 10:10:46 EDT 2011 WEB-INF/classes/com/.../CmHandler.class

  1152 Thu Oct 20 10:10:46 EDT 2011 WEB-INF/classes/com/.../LicHandler$SentinelLicenses.class

  4534 Thu Oct 20 10:10:46 EDT 2011 WEB-INF/classes/com/.../LicHandler.class

  3633 Thu Oct 20 10:10:46 EDT 2011 WEB-INF/classes/com/.../PmHandler.class

  6470 Thu Oct 20 10:10:46 EDT 2011 WEB-INF/classes/com/.../Example.class   <<-- If I do the @EJB on the Example class that exteds HttpServlet then here the @EJB works without no lookup need it.

12067 Thu Oct 20 10:10:44 EDT 2011 WEB-INF/lib/mgmt-ejb-P1A01.jar              << -- EJB ifc

  1390 Thu Oct 20 09:44:42 EDT 2011 css/test.css

  3102 Thu Oct 20 09:44:42 EDT 2011 docs/cm.html

  7051 Thu Oct 20 09:44:42 EDT 2011 docs/fm.html

  6180 Thu Oct 20 09:44:42 EDT 2011 docs/lc.html

  4034 Thu Oct 20 09:44:42 EDT 2011 docs/lm.html

  3439 Thu Oct 20 09:44:42 EDT 2011 docs/pm.html

  1929 Thu Oct 20 09:44:42 EDT 2011 images/logo.gif

  8841 Thu Oct 20 09:44:42 EDT 2011 index.jsp

[jason.greene]

Is Example some kind of EE component (a servlet, managed bea, etc)? Only declared components get EE injection.

[lmcdasi]

Example is defined as : public class Example extends HttpServlet - so it should be an EE component.

Then within the class definition I have:

    @EJB
    private ILcExample lc;

Within Example.java the @EJB injection works ok no need to specify lookup or mappedName ....

If I move that within another class that is part of the same package as Example.java the injection fails. I tried with lookup or mappedName and no success.

Only jndi lookup works on other classes. Should I add in the Manifest file a dependency to EE ?

BR,

Dan S.

[jason.greene]

Dan Sirbu wrote:

Example is defined as : public class Example extends HttpServlet - so it should be an EE component.

Then within the class definition I have:

    @EJB
    private ILcExample lc;

Within Example.java the @EJB injection works ok no need to specify lookup or mappedName ....

If I move that within another class that is part of the same package as Example.java the injection fails. I tried with lookup or mappedName and no success.

Is this other class an EE component (it is a servlet, managed bean, etc)?

[lmcdasi]

No - they are not EE components. They are plain java classes:

public class MyTestClass{

    ...

    @EJB or @EJB(lookup) or @EJB(mappedName)  - does not work - jndi lookup yes

    private ILcExample lc;

    ......

}

[jason.greene]

Dan Sirbu wrote:

No - they are not EE components. They are plain java classes:

public class MyTestClass{

    ...

    @EJB or @EJB(lookup) or @EJB(mappedName)  - does not work - jndi lookup yes

    private ILcExample lc;

    ......

}

Ok yeah, then as I mentioned above, per spec those classes are not elligible for injection (only EE components). The JNDI look up works because the classes are sharing the EE context of the component that calls them.

[lmcdasi]

OK. If I add an application.xml where I define the <module><ejb> info (e.g. : http://docs.jboss.com/books/lightweight/ch03.html) would I still be able to use the @EJB from the non EE component or I would have to re-work the classes ?

Inheriting this code from other app server so I aim as changing as little as possible .... if possible.

[jaikiran]

Dan Sirbu wrote:

OK. If I add an application.xml where I define the <module><ejb> info (e.g. : http://docs.jboss.com/books/lightweight/ch03.html) would I still be able to use the @EJB from the non EE component or I would have to re-work the classes ?

Resource injection which includes (@Resource, @EJB etc...) will not happen in a application managed class (i.e. a class whose lifecycle is managed by an application and not by the container). So ultimately, if your class is a non-EE class, then there's no server provided resource injection.  

[jason.greene]

One thing to add is that you can get injection for simple beans by either:

   1. Using CDI in which case every class can be injected and CDI controls the lifecycle

OR

   2. Making the class a managed bean and accessing it from either JNDI or EEinjection. In this case the container is controlling the creation part of the lifecycle

[lmcdasi]

Do you imply that if I use CDI or managed bean I will be able to have the @EJB or @Inject working in a non-EE class ?