-->
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 Lock -using @Version Gives Problem.
PostPosted: Wed Jul 24, 2013 2:43 am 
Newbie

Joined: Wed Jul 24, 2013 2:29 am
Posts: 1
Hi all,
Due to recent requirment in my project, I have used @version for handling Stale data, now versioning is working beautifully but it is creating problem all over the application like,
1. Retrieving - when i retrieve a data using entity which is fetched from some other transaction, it gives transient object exception.
2.Peresisting - same scenario as above entity fetched from some other transaction, it gives non null parameter or tranisent object exception
In both cases i understood the problem - the reason is the object is transient(detached from session)
without @version the above scenarios are working fine

can some one explain me why?


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.