[
https://issues.apache.org/jira/browse/OAK-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877306#comment-13877306
]
Marcel Reutegger commented on OAK-1329:
---------------------------------------
Oh, I wasn't aware of the may clause. Thanks for the pointer.
This would potentially allow us to implement Lock.getLockToken() differently in
Oak and return the lock token even when the current session does not hold the
lock token. That way client code could acquire the token from the lock and add
it to the session to become the lock holder.
> 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)
