[jira] Updated: (JCR-1733) WebDAV BIND support
[ 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
[ 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.
[jira] Updated: (JCR-1733) WebDAV BIND support
[ 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
[ 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
[ 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
[ 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] Updated: (JCR-1733) WebDAV BIND support
[ 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
[ 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
[ 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] Updated: (JCR-1733) WebDAV BIND support
[ 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
[ 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.
