Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Thu, 30 Aug 2012 20:16:08 +1100 (NCT)
From: "Gazi Mushfiqur Rahman (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <198013240.15942.1346318168294.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <610143909.44702.1326721599821.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (JCR-3208) locking a node twice yields the same
 lock token
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gazi Mushfiqur Rahman commented on JCR-3208:
--------------------------------------------

The last update on this issue was on 17th Jan, 2012! Any update on this issue? Can we get some approx date when this will be fixed and integrated in Apache Sling?

Thanks.
                
> locking a node twice yields the same lock token
> -----------------------------------------------
>
>                 Key: JCR-3208
>                 URL: https://issues.apache.org/jira/browse/JCR-3208
>             Project: Jackrabbit Content Repository
>          Issue Type: Task
>          Components: jackrabbit-core, locks
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>         Attachments: JCR-3208.diff, JCR-3208.diff
>
>
> Due to the way jackrabbit assigns lock tokens, the same lock token is generated every time a node is locked.
> This seems to contradict a JCR requirement:
> "A lock token is a string that uniquely identifies a particular lock and acts as a key granting lock ownership to any session that hold the token." <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.5%20Lock%20Token>
> ...in that two subsequent locks on the same node get the same token.
> (This may be harmless but we should consider fixing this for compliance reasons)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira