[
https://issues.apache.org/jira/browse/OAK-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876516#comment-13876516
]
Marcel Reutegger commented on OAK-1329:
---------------------------------------
Well, that's exactly the problem with the JCR spec. It isn't possible. With
Jackrabbit you have to look up the low level storage where the locks are
persisted and then use this information to unlock the node again.
> Relaxed JCR locking behavior
> ----------------------------
>
> Key: OAK-1329
> URL: https://issues.apache.org/jira/browse/OAK-1329
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Reporter: Marcel Reutegger
>
> Open scoped locks in JCR can be quite troublesome to use in practice. Mainly
> because of the requirement to remember the token generated by a lock
> operation. This token must be added again to the session when a unlock is
> called. The problematic part is where to store the token und what happens
> when the token is lost. In practice it is usually more desireable to allow
> any session autenticated for a given user to unlock the nodes for which
> he/she is the lock owner (identified by the jcr:lockOwner property).
> I suggest we make this a deployment option.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
