You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tomee.apache.org by "Andy Gumbrecht (JIRA)" <ji...@apache.org> on 2014/09/10 22:43:34 UTC

[jira] [Assigned] (OPENEJB-2100) Context Classloader not restored in org.apache.openejb.client.EJBObjectHandler.createEJBObjectProxy

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

Andy Gumbrecht reassigned OPENEJB-2100:
---------------------------------------

    Assignee: Andy Gumbrecht

> Context Classloader not restored in org.apache.openejb.client.EJBObjectHandler.createEJBObjectProxy
> ---------------------------------------------------------------------------------------------------
>
>                 Key: OPENEJB-2100
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-2100
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 4.6.0.2
>            Reporter: Thorsten Meinl
>            Assignee: Andy Gumbrecht
>             Fix For: 4.7.2, 5.0.0
>
>         Attachments: EJBObjectHandler.java.patch
>
>
> When accessing a bean via the InitialContext, the context classloader of the calling thread is changed. This causes problems in application that rely on certain context classloaders, e.g. Eclipse. The bug is quite obvious: before creating the proxy instance in line 209 of org.apache.openejb.client.EJBObjectHandler, the context classloader is changed. However, after the call is should be restored but is again set to the other classloader. The argument should be "oldCl" instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)