"[EMAIL PROTECTED]" wrote : | 4. In the case that Key is non-primitive, we shall require them to be Serializable. I think this is in line with regular POJO Cache where we require the POJO to be aspectizable (.e.g, with xml or annotation declaration), otherwise, it needs to be Serializable. | -Ben
In the case of a Set, the user can't provide the key, so we're really saying that any values put in sets have to be Serializable, plus we're going to replicate that value as part of an Fqn anytime one of its internal fields changes. So, I've got class School, one of whose fields is Set students. Student is itself a potentially large object graph; i.e. has Address with a zip field. Now I change the zip field. The zip going to be in a node whose Fqn includes the Set element node. Therefore even though I've only changed the zip, the entire student object is going to be serialized and replicated as part of the Fqn. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921596#3921596 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921596 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
