[
https://issues.apache.org/jira/browse/JCR-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187687#comment-13187687
]
Jukka Zitting commented on JCR-3208:
------------------------------------
It's probably best to raise an issue in JSR 333 for a clarification on the
uniqueness requirements on lock tokens.
> 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
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
