[
http://jira.jboss.com/jira/browse/JBCACHE-830?page=comments#action_12346675 ]
Ben Wang commented on JBCACHE-830:
----------------------------------
I have taken a look closely. Turns out that the Collection ClassProxy can actually
serializie correctly. Classes like CachedMapImpl doesn't need to be Seriaizable
because CachedMapInterceptor, e.g., will do a reflection on the CachedMapImpl. The
original forum post's problem lies elsewhere. It complains of MarshalledClassProxy
where we use only ClassProxy in Collection. So it maybe a leak from AS side. Anyway, I
think it is a corner case now.
Incorrect serialization of Collection and Map proxies
-----------------------------------------------------
Key: JBCACHE-830
URL:
http://jira.jboss.com/jira/browse/JBCACHE-830
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: PojoCache
Affects Versions: 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA,
1.2.4SP2
Reporter: Brian Stansberry
Assigned To: Ben Wang
Fix For: 2.0.0.GA
The PojoCache Collection and Map proxies implement Serializable but don't do anything
to override default serialization. They have non-transient fields with refs to things
like the cache itself, so serializing one of these is a big problem -- you serialize the
whole cache.
Not sure what the best solution to this is. Perhaps use writeReplace()?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira