[
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."
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