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/11/10 10:34:00 UTC

[jira] [Updated] (OAK-4234) NodeDelegate: checking for locks should not require read access to system lock properties

     [ https://issues.apache.org/jira/browse/OAK-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela updated OAK-4234:
------------------------
    Fix Version/s:     (was: 1.6)
                   1.8

> NodeDelegate: checking for locks should not require read access to system lock properties
> -----------------------------------------------------------------------------------------
>
>                 Key: OAK-4234
>                 URL: https://issues.apache.org/jira/browse/OAK-4234
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: jcr
>            Reporter: Julian Reschke
>            Priority: Minor
>             Fix For: 1.8
>
>
> {{isLocked()}} currently will return false when the caller does not have read access to the lock properties of the node.
> For shallow nodes this might be harmless, but for deep locks it's not (so in that case, the information is only accurate when the caller has read access to all ancestor's system properties).
> Furthermore. checking for locks might be done frequently, and could be faster when unnecessary checks would be skipped.



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