-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: Optimistic Locking without @Version
PostPosted: Wed Apr 27, 2011 7:25 am 
Beginner
Beginner

Joined: Tue Dec 21, 2010 5:26 am
Posts: 25
Hi I need to implement the optimistic locking without the use of the @Version annotation since I have a legacy database schema here. I looked at the documentation and the book and found a way to do this. But it only applies to one table. I need it to be able to notice when two threads (users) are working with object A and one is modifying an object in Set<B> and one is modifying an object in Set<C>.

I was kinda hoping optimistic locking would also detect that and throw a staleDataException or whatever it's called... but it doesn't. So my question is: How can I achieve that?


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.