[JCR-2004] Update SPI locking to match JCR 2.0

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-alpha3
• Component/s: jackrabbit-spi, JCR 2.0
• Assignee: Angela Schreiber
• Reporter: Angela Schreiber
• Created: 04/Mar/09 10:50
• Updated: 02/May/13 02:29
• Resolved: 09/Jun/09 10:04

Description

jcr2spi currently uses the JSR 170 way to determine whether a given Session owns the lock by checking of the lock token is null.
with JSR 283 a new Lock method has been defined for this, while on the other hand the lock token is always null for session-scoped
locks.

In addition 283-locking allows to specify a timeout hint and hint about the owner info that should be displayed
for information purpose.

Proposed changes to SPI:

• extend org.apache.jackrabbit.spi.LockInfo to cover the new functionality added with JSR 283
• add an variant of RepositoryService.lock that allows to specify timeout and owner hint.

Proposed changes to JCR2SPI:

• change jcr2spi to make use of the new functionality and modify the test for session being lock holder.
  this mainly affects
  > LockOperation
  > LockManager impl
  > Lock impl

Issue Links

• is depended upon by: JCR-2097 Broke lock tests in jcr2spi after the JCR 2.0 upgrade