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

• Type: Technical task
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Component/s: jcr
• Assignee: Unassigned
• Reporter: Julian Reschke
• Created: 19/Apr/16 10:29
• Updated: 16/Nov/17 08:47
• Resolved: 16/Nov/17 08:47

Description

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.

Issue Links

• relates to: OAK-6421 Phase out JCR Locking support