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 "angela (JIRA)" <ji...@apache.org> on 2013/07/25 15:13:48 UTC

[jira] [Commented] (OAK-150) Basic JCR LockManager support

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

angela commented on OAK-150:
----------------------------

no, we can't close it. 'basic' has proven to be insufficient for getting our internal test pass.
during the last oakathon we agreed that we have to add a proper implementation for non-clustered setup and provide a hook for other cases as outlined by michael above.
                
> Basic JCR LockManager support
> -----------------------------
>
>                 Key: OAK-150
>                 URL: https://issues.apache.org/jira/browse/OAK-150
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>              Labels: locking
>
> Even though we currently don't (and perhaps never will) support full JCR locking functionality in Oak, it would still be good to have a basic LockManager implementation for clients that assume it's present and use it simply to access lock tokens and to ask whether a particular node is locked or not.

--
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