[jira] [Resolved] (TOMEE-877) ParentClassLoaderFinder default strategy is broken for embedded OpenEJB

["Romain Manni-Bucau (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TOMEE-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Manni-Bucau resolved TOMEE-877.
--------------------------------------

       Resolution: Not a Problem
    Fix Version/s: 1.6.0

Since component are configurable in system.properties I guess this is fixed

> ParentClassLoaderFinder default strategy is broken for embedded OpenEJB
> -----------------------------------------------------------------------
>
>                 Key: TOMEE-877
>                 URL: https://issues.apache.org/jira/browse/TOMEE-877
>             Project: TomEE
>          Issue Type: Bug
>    Affects Versions: 1.5.1
>            Reporter: Mark Struberg
>            Priority: Critical
>             Fix For: 1.6.0
>
>         Attachments: TOMEE-877.patch
>
>
> 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. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)