Tim - I can see that it might be implemented as you say, and I've no doubt that keeping only identifiers or proxy references would solve the problem, but the requirement that we cache only the latest version of the domain objects arises directly from the fact that we have to cache them in the first place. In a nutshell, each client maintains a very interconnected graph of domain objects, subgraphs of which get sent to the server to be persisted by Hibernate. If the graph is not consistent, Hibernate will barf, as it should. If we were not caching on the client, we would not have to solve this problem. As far as I can tell, this places the responsibility more on the cache than on the objects comprising the problem domain. If we stop using the cache, then yes, the graph consistency semantics disappear, but that is exactly what we want (I think).
Anyways, it looks like JBossCache may not be the ideal solution to this problem. If anyone has any suggestions I would appreciate them! And thanks for taking the time to read my posts... Daniel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854374#3854374 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3854374 ------------------------------------------------------- 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
