You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2008/09/12 10:13:44 UTC
[jira] Created: (JCR-1733) WebDAV BIND support
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
I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manfred Baedke updated JCR-1733:
--------------------------------
Attachment: patch-rebind-unbind-resourceid.txt
Contains support for the property DAV:resource-id and the methods REBIND and UNBIND (includes patch-resourceid.txt).
> 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-rebind-unbind-resourceid.txt, patch-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manfred Baedke updated JCR-1733:
--------------------------------
Attachment: (was: ci-resourceid.txt)
> 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-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manfred Baedke updated JCR-1733:
--------------------------------
Attachment: patch-resourceid.txt
patch containing support for DAV:resource-id
> 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-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Commented: (JCR-1733) WebDAV BIND support
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631799#action_12631799 ]
Julian Reschke commented on JCR-1733:
-------------------------------------
Looks good to me so far.
Maybe we can re-use org.apache.jackrabbit.uuid.UUID for the UUID parsing?
> 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: ci-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Commented: (JCR-1733) WebDAV BIND support
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633197#action_12633197 ]
Julian Reschke commented on JCR-1733:
-------------------------------------
Applied first patch (DAV:resource-id) with revision 697767.
> 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-rebind-unbind-resourceid.txt, patch-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Commented: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ 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 jackrabbit-core.
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 http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manfred Baedke updated JCR-1733:
--------------------------------
Attachment: patch-bindsupport.txt
patch containing support for WebDAV binding extensions.
> 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 http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Commented: (JCR-1733) WebDAV BIND support
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634513#action_12634513 ]
Julian Reschke commented on JCR-1733:
-------------------------------------
The latest patch looks good to me so far (except one typo in pom.xml :-), I'd propose to apply it soonish (in the meantime more tests can be added).
> 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 http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Resolved: (JCR-1733) WebDAV BIND support
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-1733.
---------------------------------
Resolution: Fixed
Applied Manfred's patch (plus some minor changes to documentation) with revision 700097.
> 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: jcr1733-bindsupport.patch, patch-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manfred Baedke updated JCR-1733:
--------------------------------
Attachment: (was: patch-rebind-unbind-resourceid.txt)
> 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-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manfred Baedke updated JCR-1733:
--------------------------------
Attachment: patch-bindsupport.txt
Added client components and testcases.
The test org.apache.jackrabbit.webdav.server.BindTest.testUnbind() currently fails due to the jackrabbit-core issue JCR-1773.
> 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 http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manfred Baedke updated JCR-1733:
--------------------------------
Attachment: (was: patch-bindsupport.txt)
> 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-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manfred Baedke updated JCR-1733:
--------------------------------
Attachment: ci-resourceid.txt
patch containing support for DAV:resource-id
> 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: ci-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Commented: (JCR-1733) WebDAV BIND support
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632200#action_12632200 ]
Julian Reschke commented on JCR-1733:
-------------------------------------
Looks good to me.
I'll commit this soonish unless somebody can spot a problem with this little extension...
> 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-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-1733:
------------------------
Fix Version/s: 1.5
Issue Type: New Feature (was: Task)
> WebDAV BIND support
> -------------------
>
> Key: JCR-1733
> URL: https://issues.apache.org/jira/browse/JCR-1733
> Project: Jackrabbit
> Issue Type: New Feature
> Components: jackrabbit-webdav
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 1.5
>
> Attachments: jcr1733-bindsupport.patch, patch-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manfred Baedke updated JCR-1733:
--------------------------------
Attachment: (was: patch-bindsupport.txt)
> 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-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
Posted by "Manfred Baedke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manfred Baedke updated JCR-1733:
--------------------------------
Attachment: jcr1733-bindsupport.patch
removed changes from AbstractResource (belongs to JCR WebDAV, not Simple WebDAV)
> 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: jcr1733-bindsupport.patch, patch-resourceid.txt
>
>
> I'm tempted to work on implementing the WebDAV BIND protocol, as currently defined in http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-20.html.
> 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.