Did you ever find a workaround for this or a fix.
We are experiencing the same problem with Jboss 4.0.2.
In our application we have one EJB which needs to call
a service in another one in order to get data, however
the initial context lookup fails.
Thanks Scott. I looked at the source code and figured out the fact that local-jndi-name has to be specified. I think this is the best way to handle this.
On a side note what I did before doing the local-jndi-name is using a bit of the JMX notifications that are fired in JBoss to handle this dependency locally. Basically at MBean deployment time (start() method being called) the MDB is checked if it was deployed, if not I subscribe to the 'service started' JMX notification and when the MDB gets deployed the code in the start() method of the MBean is executed. I would not recommend this method necessarily since the specifying of the local-jndi-name is easier and reuses the JBoss dependency resolver but it could be used for some other cases.