tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENEJB-1321) What classloader to add generated proxies to?
Date Thu, 05 Aug 2010 05:40:17 GMT

    [ https://issues.apache.org/jira/browse/OPENEJB-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895555#action_12895555
] 

David Jencks commented on OPENEJB-1321:
---------------------------------------

rev 982475.

> What classloader to add generated proxies to?
> ---------------------------------------------
>
>                 Key: OPENEJB-1321
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1321
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: container system
>    Affects Versions: 3.2
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.2
>
>
> LocalBeanProxyGeneratorImpl is generating proxies and adding them to a supplied classloader
using the protection domain of the LocalBeanProxyGeneratorImpl class itself.
> The supplied classloader appears to be the one for the module.
> This isn't working in the geronimo integration, where the classloader delegates all classloading
to an underlying osgi bundle without checking for any classes that Unsafe might have tacked
onto the classloader itself.
> What seems to work OK in openejb and geronimo is to add the proxy to the classloader
of the original class being proxied and use the protection domain for this class also.  I'm
opening this jira because I'm not sure if there will be undesirable consequences I haven't
found yet.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message