[jboss-jira] [JBoss JIRA] Commented: (JASSIST-109) Better way to designate classloader to use for proxies that supports OSGi

[Pete Muir (JIRA)]

    [ https://jira.jboss.org/jira/browse/JASSIST-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12519308#action_12519308 ] 

Pete Muir commented on JASSIST-109:
-----------------------------------

Which obviously raises it head in OSGi, as the SerializationProxy is an internal implementation detail, not something you want to export as one of the APIs. However, as a classloader other than the one loading Javassist needs to use it when deserializing you must export it. Ouch!

> Better way to designate classloader to use for proxies that supports OSGi
> -------------------------------------------------------------------------
>
>                 Key: JASSIST-109
>                 URL: https://jira.jboss.org/jira/browse/JASSIST-109
>             Project: Javassist
>          Issue Type: Feature Request
>            Reporter: Pete Muir
>            Assignee: Shigeru Chiba
>
> The big problem we have encountered with OSGi support so far is that the classloader for deserializing proxies is very coarse grained to set

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira