If you need the cache to enforce fine-grained control over the internals of mutable cached objects, you need to use PojoCache (fka TreeCacheAop).
As ajoe stated, otherwise enforcing such control would mean the cache would have to clone all objects before returning them. But who knows if cached objects are Clonable? And how do they implement cloning -- is it a shallow copy or a deep one? What seems to be missing here is some kind of analogue to SELECT FOR UPDATE -- i.e. a getForUpdate() for Step 2 of the sequence which would then acquire a write lock on the node instead of a read lock. The presence of the WL would then prevent Process B reading the node until the tx commits. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3943623#3943623 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3943623 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
