|> Why? Because Serialization includes the private state of the
|> object. This is
|> a perfectly valid PK which is not handled correctly by CacheKey. If the
|> _hashCode value is marked as transient all works. The assumption being
|> made by CacheKey is that the only ivars in the PK are its fields
|> that define
|> its identity.
I see, so we must generate the cachekey values by serializing only the
relevant fields.... pfffff here comes complexity.
hmmmm
marcf
|>
|>
|>
|>
|> _______________________________________________
|> Jboss-development mailing list
|> [EMAIL PROTECTED]
|> http://lists.sourceforge.net/lists/listinfo/jboss-development
|>
|
|
|_________________________________________________________
|Do You Yahoo!?
|Get your free @yahoo.com address at http://mail.yahoo.com
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
