jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manfred Baedke (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1733) WebDAV BIND support
Date Thu, 25 Sep 2008 14:25:44 GMT

    [ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634493#action_12634493

Manfred Baedke commented on JCR-1733:

The file patch-bindsupport.txt covers all five issues mentioned by Julian, together with the
necessary changes to the OPTIONS method and the handling of the DAV header.
It should be noted that DELETE may remove the wrong binding, which is a separate issue concerning
Cycle detection is not implemented at WebDAV level, since the current jackrabbit core does
not allow cycles anyway.

> WebDAV BIND support
> -------------------
>                 Key: JCR-1733
>                 URL: https://issues.apache.org/jira/browse/JCR-1733
>             Project: Jackrabbit
>          Issue Type: Task
>          Components: jackrabbit-webdav
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>         Attachments: patch-bindsupport.txt, patch-resourceid.txt
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in
> This issue can be used to collect design proposals and track progress.
> 1) DAV:resource-id live property
> This can be implemented in terms of the JCR UUID. However, we need to turn this one into
a URI for WebDAV. If the JCR UUID happens to *really* use UUID syntax, we *could* use urn:uuid.
Otherwise, it would probably useful to mint an HTTP URI, served by the WebDAV servlet. (note
that the latter has the disadvantage that moving a node to a different server will affect
its resource-id, in case that other server allows importing UUIDs).
> 2) REBIND and UNBIND methods
> Same as MOVE and DELETE, with the excpetion of marshalling.
> 3) DAV:parent-set property
> Either trivial (when node isn't shared), or needs to use the JCR 2.0 shared set functionality.
> 4) BIND method
> Either trivial (when shareable nodes aren't supported), or needs to use the JCR 2.0 shared
set functionality.
> 5) Cycle detection in depth:infinity requests
> TBD :-)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message