You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2009/04/07 16:21:13 UTC

[jira] Issue Comment Edited: (JCR-1590) JSR 283: Locking

    [ https://issues.apache.org/jira/browse/JCR-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681713#action_12681713 ] 

angela edited comment on JCR-1590 at 4/7/09 7:19 AM:
-----------------------------------------------------

rev. 753244  

- session-scoped locks must not expose the lock token
  -> see also changes made to jackrabbit-spi, jackrabbit-jcr2spi and spi-impls
- WorkspaceImpl implements the 283-Workspace
  -> renamed the implementation specific getLockManager method to getInternalLockManager
  -> and changed its usage accordingly
- getSecondsRemaining returns a negative number if the lock has expired or was released.

TODO:

- timeout 
- adjust/review TCK tests and merge with 283 tests 
- LockException should have the failure-node-path set

      was (Author: anchela):
    rev. 753244  

- session-scoped locks must not expose the lock token
  -> see also changes made to jackrabbit-spi, jackrabbit-jcr2spi and spi-impls
- WorkspaceImpl implements the 283-Workspace
  -> renamed the implementation specific getLockManager method to getInternalLockManager
  -> and changed its usage accordingly
- getSecondsRemaining returns a negative number if the lock has expired or was released.

TODO:

- timeout 
- adjust/review TCK tests and merge with 283 tests 
  
> JSR 283: Locking
> ----------------
>
>                 Key: JCR-1590
>                 URL: https://issues.apache.org/jira/browse/JCR-1590
>             Project: Jackrabbit Content Repository
>          Issue Type: Sub-task
>          Components: JCR 2.0
>            Reporter: angela
>             Fix For: 2.0.0
>
>


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