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

[boru]

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>

[ldevrie]

I am encountering a similiar problem, and according to what I have been seeing the in the code, the ejb-local-ref is not a valid tag in the jboss-web.xml. I also did not see the ejb-local-ref tag in the DTD either.

However, I would also say that changing to just a ejb-ref tag will not fix that problem either, as it appears that the AbstractWebContainer keeps local refs separate from remotes.

Not much help, as I am also having the same problem.

[boru]

the reference to jboss-web.xml was a "red herring", I completely removed it as suggested by Juha in his response to you. It still works just fine with only the documented ejb-jar.xml entries in Jboss 3.2.1+tomcat and still fails in the same way I mentioned in previous post for 3.2.2RC1+tomcat.