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

Posted to oak-dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2012/06/25 15:31:42 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=13400466#comment-13400466 ] 

Julian Reschke commented on OAK-150:
------------------------------------

As far as I recall, MS Office (when using WebDAV) expects:

- that the LOCK operation succeeds and returns a lock token
- that timeout information is preserved and actually works (if the lock token is lost)
- that the lock token can be discovered (WebDAV DAV:lockdiscovery)

Support for user-supplied owner information probably might not be necessary anymore.

The MacOS webdav stack IMHO also tries to LOCK and will otherwise fail (?). Dunno what features it needs specifically.


                
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira