EHC ❯ Persistent feature using custom ObjectInputStream
-
Bug
-
Status: Closed
-
-
Resolution: Fixed
-
-
-
drb
-
Reporter: sourceforgetracker
-
September 21, 2009
-
0
-
Watchers: 0
-
September 22, 2009
-
September 22, 2009
Description
The persistent feature is very useful, but causes troubles when you want to store objects with properties belonging to a referential.
For instance :
// Property class class SampleProperty implements Serializable { … (set of serializable properties) }
// Class that MUST contains all instances of SampleProperty class PropertyReferential { … }
// Class of object to store in a persistent cache class ObjectToCache implements Serializable { SampleProperty m_prop1; … other properties }
When you directly create ObjectToCache, you can control that all m_prop1 properties are belonging to the PropertyReferential.
But when you unserialize an ObjectToCache instance, the SampleProperty m_prop1 is not automaticaly added to the PropertyReferential …
To enable this, whe should replace the ObjectInputStream in the net.sf.ehcache.store.DiskStore.java class by a “Custom” ObjectInputStream that handles properly the created objects.
I should suggest an optionnaly method based on “ClassForName” that’s allow use of a Custom ObjectInputStream instead of the ObjectInputStream.
Thanks. Sourceforge Ticket ID: 1049971 - Opened By: nobody - 19 Oct 2004 11:55 UTC
Re-opening so that I can properly close out these issues and have correct Resolution status in Jira