[OAK-3482] Lock object spec compliance issue

• Type: Technical task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.0.21, 1.2.6, 1.3.7
• Component/s: jcr
• Assignee: Unassigned
• Reporter: Julian Reschke
• Created: 06/Oct/15 12:20
• Updated: 16/Nov/17 08:45
• Resolved: 16/Nov/17 08:45

Description

The Lock object does not have any knowledge about whether a locked node has been locked session-scoped or open-scoped. Consequently, getLockToken() for a session-scoped lock can return the lock token although it should not. This causes the test failure in org.apache.jackrabbit.test.api.lock.LockTest#testNodeLocked.

Issue Links

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