Hi Claus Thank you for your answer. I already went through the jcr specification, but unfortunately it doesn't provide any real help for this problem. The test case already does the locking and unlocking in two separate transactions, as suggested in 17.10. The description in the specification basically fits exactly to our case, with the step they call "do B" being our move operation. Also when checking the lock before or in the second transaction, we see that the node is indeed locked between the transaction, so this is not the issue.
I don't think that this is a problem regarding jcr, but with the way it is implemented in jackrabbit. Whether it's a bug or it's intended behavior and I misunderstood something, I can't say. Kind regards, Thomas -----Original Message----- From: KÖLL Claus [mailto:[email protected]] Sent: Mittwoch, 22. April 2015 18:31 To: [email protected] Subject: AW: Move, Locks and Transactions Hi Thomas, Please have a look at http://www.day.com/specs/jcr/2.0/17_Locking.html In the Section "17.10 Locks and Transactions" you will find how jackrabbit handles Locks within Transactions .. greets claus
