I have several EJBs, which use a service library. This service library in turn makes use of another EJB.
Right now (JBoss 2.4), the service library makes a hardcoded lookup on the global JNDI namespace ("ejb/ServiceBean") and casts the returned reference to the corresponding home interface.
With JBoss 3.2, I get a ClassCastException.
Do I have to add an EJB reference to the deployment descriptor for every single EJB which uses the service library? And then I would have to change the service library to make a lookup on "java:/comp/env/..."? Or is there a possibility to avoid this?
I just found the chapter about the new ClassLoader architecture in the Admin+Development documentation.
The problem has nothing to do with EJB references but with the classloader: I am calling an EJB of a different ear and this ear has its own classloader (jboss-app.xml).