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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2017/11/16 08:48:00 UTC
[jira] [Resolved] (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 ]
Marcel Reutegger resolved OAK-4234.
-----------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 1.8)
WONTFIX because Oak is phasing out JCR Lock support (OAK-6421).
> 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
>
> {{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.4.14#64029)