The end goal is not for that last false to be true, so it's not enough for me to just change that portion of the code. The end goal is that when I implement custom equality logic in my domain objects, the cache uses that logic to ensure that only the most recent instance of any given domain object is ever in the cache, regardless of how many other domain objects reference them. Testing whether the two addresses were equal using == rather than .equals() was just a way of verifying that.
Basically, if Joe and Mary and their shared Address are in the cache, but I reload Mary (and her Address) from the database and stick her in the cache again, I need Joe to automatically reference the newer Address that Mary references. If I were to modify the JBossCache source to behave this way, what class(es) would I need to look at? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854289#3854289 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3854289 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
