[jira] [Commented] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers

JIRA jira@apache.org

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

Julian Reschke commented on JCR-3901:
-------------------------------------

trunk: [r1796980|http://svn.apache.org/r1796980]


> TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
> -------------------------------------------------------------------------------------
>
>                 Key: JCR-3901
>                 URL: https://issues.apache.org/jira/browse/JCR-3901
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.10.1, 2.8.1, 2.11.0
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>              Labels: candidate_jcr_2_10, candidate_jcr_2_12, candidate_jcr_2_14, candidate_jcr_2_8
>             Fix For: 2.16, 2.15.3
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's always illegal to add lock tokens to multiple sessions, however <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows simultaneous lock ownership for open scoped locks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)