[ http://issues.apache.org/jira/browse/IBATIS-73?page=comments#action_62491 ] Brandon Goodin commented on IBATIS-73: --------------------------------------
"Since EHCache requires Serializable value object, our real value object gets disassembled into Serializable components and back at retrieval." The assemble/dissasemble is pretty cool stuff. But, i'm not sure it is something we want in the iBatis framework. --- The ehcache FAQ states --- Can non-Serializable objects be stored in a cache? No. Both keys and values must be Serializable. The reason is they must be Serializable to be persisted to the DiskStore. If the type was Object and not Serializable, runtime UnserializableExceptions would be thrown when an Element is transferred to the DiskStore. As it is now, your keys and values must be Serializable or you will get a compile-time error. --- end --- I think this is the responsibility of the developer to mark their classes as serializable. I'd prefer to remove the assemble/disassemble functionality from the ehcache impl. Perhaps we can provide a hook to allow this kind of customized behavior when we make the CacheModel more flexible. Thoughts? > EHCache for iBatis > ------------------ > > Key: IBATIS-73 > URL: http://issues.apache.org/jira/browse/IBATIS-73 > Project: iBatis for Java > Type: New Feature > Components: SQL Maps > Versions: 2.0.9 > Reporter: Ales Justin > Attachments: ehcache_patch.zip, ehcache_patch_2.zip > > I have written a EHCache (http://ehcache.sourceforge.net/) implementation of > CacheController. > If there is any interest for this patch, I can send it or put it somewhere. > Rgds, Ales -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
