• Bug
  • Status: Closed
  • Resolution: Fixed
  • drb
  • Reporter: sourceforgetracker
  • September 21, 2009
  • 0
  • Watchers: 0
  • September 22, 2009
  • September 22, 2009


I believe it should not be requirement for objects to be Serializable in order to store them in a cache. This would only be the case for elements that are to be serialized to disk. I think it is the responsibility of the client application to make sure non-Serializable objects are not stored inside a disk-backed cache.

In Cocoon we’d like to also be able to use ehcache for our transient storage but can’t because of the Serializable requirement. My suggestion is to loosen the contract by changing the Element constructor to take Objects instead of Serializalbles.

Sourceforge Ticket ID: 1039390 - Opened By: nobody - 3 Oct 2004 12:35 UTC


Fiona OShea 2009-09-22

Re-opening so that I can properly close out these issues and have correct Resolution status in Jira