Well, two things in terms of data integrity for PojoCache. 1) When you try to attach/detach/retrieve POJO, yes, you are correct, I only lock put/removeObject but not getObject. I have debated about this. In the end, I have decided not to because:
a) The usage pattern for getObject is to retrieve the POJO referece. And most of the time, it will be just an get(fqn, AOPInstance.Key). So locking the whole tree doesn't do much semantically. b) The most usage for PojoCache should not be put/removeOjbect. Instead, it should be just POJO operations, e.g., pojo.setName(), etc. So in this sense, the node level REPEATABLE_READ semantics should still apply. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951812#3951812 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951812 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
