[OAK-4458] LockImpl.isLockOwningSession not consistent with unlock-capability

• Type: Technical task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: jcr
• Assignee: Unassigned
• Reporter: Angela Schreiber
• Created: 10/Jun/16 08:39
• Updated: 10/Nov/16 08:36

Description

Lock.isLockHoldingSession is IMO the only way a given application can find out if a given session can unlock a lock node (in contrast to Lock.getLockOwner which by API contract is not suited for that purpose).

However, the implementation in oak-jcr is not consistent with the unlock implementation and with the internal method LockManagerImpl.canUnlock(NodeDelegatee).