-->
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: Not using versioning for Optimistic Locking...
PostPosted: Tue Sep 04, 2012 1:32 pm 
Newbie

Joined: Tue Sep 04, 2012 1:20 pm
Posts: 1
My current client does not wish to use the versioning feature of JPA/Hibernate at this time. They do not see the need for it. I could argue differently, but that is not my call at this point. So, my question is rather simple. Do I have to do ANYTHING in order to turn off versioning/optimistic locking? I was hoping it would just work out of the box that way. I shoudl also note that it is a goal if possible to NOT reference hibernate in any of my source code (trying to stay provider neutral at this point). I have read something in another post that suggests that it is disabled unless you configure it, however I want to be sure there is not extra comparing going on during each commit (I want to retain control of that). Thank you in advance for any help!


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.