jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-2004) Update SPI locking to match JCR 2.0
Date Wed, 04 Mar 2009 10:51:56 GMT
Update SPI locking to match JCR 2.0
-----------------------------------

                 Key: JCR-2004
                 URL: https://issues.apache.org/jira/browse/JCR-2004
             Project: Jackrabbit Content Repository
          Issue Type: Sub-task
            Reporter: angela
            Assignee: angela


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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message