I get this exception in the following scenario 1. I have a class that has a 1:n relationship with a child class. 2. I add a new child to the parent, it works fine. 3. Another user then adds another child to the relationship and it fails because of an OptimisticLockExcpetion 4. The other user then refreshes his copy of the parent object and tries again with the same child object (same java reference that previously failed due to OptLock)
At this point, the above exception is being generated. If I then "clone" the child object so that the Java reference changes, everything works fine. Is this a bug on my side or a possible hibernate bug ? Any help will be appreciated. Thank You View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966895#3966895 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966895 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
