"bstansberry(a)jboss.com" wrote : You know, DefaultDataVersion causes me all sorts of troubles -- always having to worry about obscure cases where it gets assigned to a node and then conflicts with the custom DataVersion types Hibernate uses. Seems like this is something that can be improved. Perhaps make the "default" DataVersion class configurable. I could then set it to use Hibernate's NonLockingDataVersion (always returns "false" to newerThan()) instead of DefaultDataVersion. It's then my responsibility to manage versioning. That is a good idea, only it's a bit late in the day to introduce something like this now. Let me have a think, if it does make sense then I'll do it, otherwise will work with your proposed fix. Thanks for bringing this up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133870#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...