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

[David Lloyd (JIRA)]

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

David Lloyd commented on JASSIST-109:
-------------------------------------

This is the exact reason why problems like JASSIST-42 should be solved by the serialization framework, not by serialization proxies.  By delegating to the deserializer (either an extended OIS with a custom class resolver or e.g. JBoss Marshalling), classes can be looked up in an extensible fashion, and in addition, the proxy data will get serialized in the standard way.

> 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