Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Java-SCA-1.2
-
None
Description
The EJB binding invoker seems to just rely on the classloader present on the current thread context to resolve EJB interface classes returned from a JNDI lookup of the EJB.
This causes a ClassNotFoundException in the EJB interface specified on the reference is coming from another classloader than the current thread context classloader. This will likely cause similar issues with the EJB method parameter classes as well.
A quick fix for release 1.2 is to set that classloader on the current thread context before calling the invoker's doInvoke method.
A longer term fix will require more investigation.