Description
similar to OAK-9966 for Node.isLocked which calls LockManager.isLocked(String absPath). This results in the Tree object to be resolved again from the absolute path, when it was already there for the Node object.
the same applies for
- version operations that check for the node being locked
- import operation that checks for the target node being locked.
NOTE: this pattern applies for all other lock related methods. but since JCR locking is not properly implemented, i suggest to focus on the Node.isLocked and LockManager.isLocked methods, which are called frequently in code that is just performing regular writes.
cc: joerghoh
Attachments
Issue Links
- relates to
-
OAK-9984 FlatFileSplitterTest reliably failing
-
- Closed
-
- links to