You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2014/02/04 22:50:16 UTC

[jira] [Assigned] (OAK-1329) Relaxed JCR locking behavior

     [ https://issues.apache.org/jira/browse/OAK-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting reassigned OAK-1329:
----------------------------------

    Assignee: Jukka Zitting

> 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
>            Assignee: Jukka Zitting
>
> 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)