LockParentForChildInsertRemove works with both optimistic and pessimistic locking.
You won't receive a null in your above scenario since the write (in this case, the
remove() call) will not be visible to other threads until the transaction commits.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104698#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...