[ https://jira.jboss.org/jira/browse/JASSIST-109?page=com.atlassian.jira.pl... ] Shigeru Chiba commented on JASSIST-109: --------------------------------------- Any suggestion is welcome! -- 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

[ https://jira.jboss.org/jira/browse/JASSIST-109?page=com.atlassian.jira.pl... ] 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. -- 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

[ https://jira.jboss.org/jira/browse/JASSIST-109?page=com.atlassian.jira.pl... ] Pete Muir commented on JASSIST-109: ----------------------------------- This is from Sahoo, a GlassFish engineer/OSGi guy at Sun (now Oracle): "I am not sure why the test is using ObjectInputStream and ObjectOutputStream to read & write managed beans. In GlassFish, we use specialized ObjectInputStream and ObjectOutputStream to read and write container managed objects. Those specialized streams contain extra data like OSGi bundle details for a class. I would expect managed bean container to have an SPI which an appserver can use to provide suitableObjectInputStream and ObjectOutputStream objects for use. I think this is something to think about in future." -- 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

[ https://jira.jboss.org/jira/browse/JASSIST-109?page=com.atlassian.jira.pl... ] 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! -- 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