Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Not A Problem
-
1.5.1
-
None
-
None
Description
ParentClassLoaderFinder default strategy always uses the ClassLoader which got used to load OpenEJB.class. But this algorithm is broken for all scenarios where a classloader hierarchy is in place.
Instead of this we should use the Thread.currentThread.getContextClassLoader() by default.
Please note that is is effectively not possible to set a custom ParrentClassLoaderFinder (via SystemInstance.get().setComponent(ParentClassLoaderFinder.class,... ) when using EJBContainer.createEJBContainer() as this gets cleared via SystemInstance.reset() at boot time.
Attachments
Attachments
Issue Links
- is related to
-
TOMEE-2458 Loading Beans causes ClassNotFoundException when using custom context classloader
- Closed