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

[jira] Resolved: (JCR-822) TCK: Transfer of lock token should be tested using open-scoped locks

     [ https://issues.apache.org/jira/browse/JCR-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved JCR-822.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4

Committed patch in revision: 553227

> TCK: Transfer of lock token should be tested using open-scoped locks
> --------------------------------------------------------------------
>
>                 Key: JCR-822
>                 URL: https://issues.apache.org/jira/browse/JCR-822
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: JCR TCK
>            Reporter: angela
>            Priority: Minor
>             Fix For: 1.4
>
>         Attachments: tck.patch
>
>
> despite the fact that jsr170 does not limit the usage of Session.removeLockToken(String) and Session.addLockToken(String) to tokens obtained from open-scoped locks, i don't see too much benefit of it. Therefore (and due to the fact that this issue will be addressed within the scope of jsr283), i would  like to suggest to modify those test-cases dealing with transfer of lock tokens and create open-scoped locks.

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