2 Replies Latest reply on Jul 1, 2003 1:59 PM by Rick Shaw

    New Bug cropped into 3.2.2.RC1+Tomcat referencing local ejb

    Rick Shaw Newbie

      I have an ear that is made up of a very simple local stateless session EJB,
      which is accessed by a servlet deployed in a WAR file.

      It works fine all the way up to and including Jboss 3.2.1 with appropriate Tomcat.

      However it fails under Jboss3.2.2RC1 at run time with no deployment errors.

      I refer to it in the servlet as:

      this.initial = new InitialContext(); // Save the initial Context
      this.myHome = (MyLocalHome)this.initial.lookup("java:comp/env/ejb/MyEJB");
      this.myLocal = this.myHome.create();

      The error thrown at run time is tha the ENV context is not bound. Specifically it says:

      "javax.naming.NameNotFoundException: env not bound"

      I have checked and it has a "jboss:comp" context but nothing in it.

      The same EXACT ear can be deployed on the same windows 2000 config whit Jboss 3.2.1
      or earlier and works just fine.

      Is this a bug? Is it a tightening of deployment descriptor requirements??

      the end of the web.xml is:

      .
      .
      .
      .
      <ejb-local-ref>
      <ejb-ref-name>ejb/MyEJB</ejb-ref-name>
      <ejb-ref-type>Session</ejb-ref-type>
      <local-home>com.me.MyLocalHome</local-home>
      com.me.MyLocal
      <ejb-link>TheEJB</ejb-link>
      </ejb-local-ref>
      </web-app>


      and the jboss-web.xml :

      <?xml version="1.0" encoding="UTF-8"?>
      <jboss-web>
      <ejb-local-ref>
      <ejb-ref-name>TheEJB</ejb-ref-name>
      <jndi-name>app/local/MyLtttleEjb</jndi-name>
      </ejb-local-ref>
      </jboss-web>