[
https://issues.apache.org/jira/browse/JCR-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681720#action_12681720
]
angela commented on JCR-2004:
-----------------------------
committed patches at rev. 753244 (trunk) and rev. 753248 (sandbox)
TODO:
- timeout (impl missing with jackrabbit-core -> not tested)
- remove tmp dependencies to jackrabbit-api and pseudo-283 interfaces (jcr2spi,
spi2jcr, jcr-server)
- merge jcr2spi locking tests to jackrabbit-jcr-tests
> 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
> Components: jackrabbit-spi, JCR 2.0
> Reporter: angela
> Assignee: angela
> Attachments: JCR-2004-jcr-server.patch, JCR-2004-jcr2spi.patch,
> JCR-2004-sandbox.patch, JCR-2004_spi.patch
>
>
> 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.
