You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2016/06/10 08:40:21 UTC

[jira] [Created] (OAK-4458) LockImpl.isLockOwningSession not consistent with unlock-capability

angela created OAK-4458:
---------------------------

             Summary: LockImpl.isLockOwningSession not consistent with unlock-capability
                 Key: OAK-4458
                 URL: https://issues.apache.org/jira/browse/OAK-4458
             Project: Jackrabbit Oak
          Issue Type: Technical task
          Components: jcr
            Reporter: angela


{{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)}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)