[jira] Created: (SLING-342) Enable WebDAV to the Sling default workspace through Sling

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (SLING-342) Enable WebDAV to the Sling default workspace through Sling

Andrei Shilov (Jira)
Enable WebDAV to the Sling default workspace through Sling
----------------------------------------------------------

                 Key: SLING-342
                 URL: https://issues.apache.org/jira/browse/SLING-342
             Project: Sling
          Issue Type: New Feature
          Components: Repository
            Reporter: Felix Meschberger
            Assignee: Felix Meschberger
             Fix For: 2.0.0


Currently, the jcr/webdav module provides WebDAV through the SimpleWebDavServlet in its own servlet context (configurable, default is /dav). This default support requires including the name of the workspace to access in the URL.

Additional support for WebDAV should be added which allows WebDAV access to the default workspace used by Sling through the Sling Main Servlet. As such, a Sling Servlet is to be registered which implements WebDAV.

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


Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (SLING-342) Enable WebDAV to the Sling default workspace through Sling

Andrei Shilov (Jira)

     [ https://issues.apache.org/jira/browse/SLING-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-342.
-------------------------------------

    Resolution: Fixed

Committed SlingWebDavServlet in Rev. 640960, which is a default servlet handling all requests for which there is no more specific servlet. In particular this handles all WebDAV specific request methods.

For now, I set this issue resolved. There are some integration tests failing on my local machine. Will have to invetigate this before closing this issue.

> Enable WebDAV to the Sling default workspace through Sling
> ----------------------------------------------------------
>
>                 Key: SLING-342
>                 URL: https://issues.apache.org/jira/browse/SLING-342
>             Project: Sling
>          Issue Type: New Feature
>          Components: Repository
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Currently, the jcr/webdav module provides WebDAV through the SimpleWebDavServlet in its own servlet context (configurable, default is /dav). This default support requires including the name of the workspace to access in the URL.
> Additional support for WebDAV should be added which allows WebDAV access to the default workspace used by Sling through the Sling Main Servlet. As such, a Sling Servlet is to be registered which implements WebDAV.

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


Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SLING-342) Enable WebDAV to the Sling default workspace through Sling

Andrei Shilov (Jira)
In reply to this post by Andrei Shilov (Jira)

    [ https://issues.apache.org/jira/browse/SLING-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582059#action_12582059 ]

Bertrand Delacretaz commented on SLING-342:
-------------------------------------------

CreateNodeTest fixed in revision 640986, the difference is that unsupported URLs in GET requests now return a 404 status instead of 500, which is fine.

Also tried to update launchpad/webapp/pom.xml to use the / path as the base for WebDAV operations in revision 640987, so that this new servlet is used for the launchpad integration tests by default.

Integration tests passed when run with the Sling webapp mounted on /, but not if mounted on org.apache.sling.launchpad.webapp-2.0.0-incubator-SNAPSHOT/ - probably a minor path concatenation problem, reverted the pom.xml change, will look at that tomorrow unless someone beats me to it.

> Enable WebDAV to the Sling default workspace through Sling
> ----------------------------------------------------------
>
>                 Key: SLING-342
>                 URL: https://issues.apache.org/jira/browse/SLING-342
>             Project: Sling
>          Issue Type: New Feature
>          Components: Repository
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Currently, the jcr/webdav module provides WebDAV through the SimpleWebDavServlet in its own servlet context (configurable, default is /dav). This default support requires including the name of the workspace to access in the URL.
> Additional support for WebDAV should be added which allows WebDAV access to the default workspace used by Sling through the Sling Main Servlet. As such, a Sling Servlet is to be registered which implements WebDAV.

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


Reply | Threaded
Open this post in threaded view
|

[jira] Reopened: (SLING-342) Enable WebDAV to the Sling default workspace through Sling

Andrei Shilov (Jira)
In reply to this post by Andrei Shilov (Jira)

     [ https://issues.apache.org/jira/browse/SLING-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger reopened SLING-342:
-------------------------------------


Reopening this issue. The problems you encountered with the integration tests might be related to iincorrect handling of the servlet context path in SlingWebDavServlet.

> Enable WebDAV to the Sling default workspace through Sling
> ----------------------------------------------------------
>
>                 Key: SLING-342
>                 URL: https://issues.apache.org/jira/browse/SLING-342
>             Project: Sling
>          Issue Type: New Feature
>          Components: Repository
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Currently, the jcr/webdav module provides WebDAV through the SimpleWebDavServlet in its own servlet context (configurable, default is /dav). This default support requires including the name of the workspace to access in the URL.
> Additional support for WebDAV should be added which allows WebDAV access to the default workspace used by Sling through the Sling Main Servlet. As such, a Sling Servlet is to be registered which implements WebDAV.

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


Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (SLING-342) Enable WebDAV to the Sling default workspace through Sling

Andrei Shilov (Jira)
In reply to this post by Andrei Shilov (Jira)

     [ https://issues.apache.org/jira/browse/SLING-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-342.
-------------------------------------

    Resolution: Fixed

The problem with WebDAV setting to "/" is not actually the SlingWebDavServlet but the HttpTestBase accessing the WebDAV root without a trailing slash. This causes and access to the context path root without a trailing slash causing the servlet container to send back a redirect.

Appending a trailing slash to the check causes the test to succeed.

> Enable WebDAV to the Sling default workspace through Sling
> ----------------------------------------------------------
>
>                 Key: SLING-342
>                 URL: https://issues.apache.org/jira/browse/SLING-342
>             Project: Sling
>          Issue Type: New Feature
>          Components: Repository
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Currently, the jcr/webdav module provides WebDAV through the SimpleWebDavServlet in its own servlet context (configurable, default is /dav). This default support requires including the name of the workspace to access in the URL.
> Additional support for WebDAV should be added which allows WebDAV access to the default workspace used by Sling through the Sling Main Servlet. As such, a Sling Servlet is to be registered which implements WebDAV.

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


Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (SLING-342) Enable WebDAV to the Sling default workspace through Sling

Andrei Shilov (Jira)
In reply to this post by Andrei Shilov (Jira)

     [ https://issues.apache.org/jira/browse/SLING-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed SLING-342.
-----------------------------------


Integration tests succeed also when using the same path as the WebDAV base as for plain HTTP. So I set the integration tests to the root in Rev. 641192.

The problem with the integration tests is fixed in the HttpTestBase class in Rev. 641191.

Now, therefore I close this issue.

> Enable WebDAV to the Sling default workspace through Sling
> ----------------------------------------------------------
>
>                 Key: SLING-342
>                 URL: https://issues.apache.org/jira/browse/SLING-342
>             Project: Sling
>          Issue Type: New Feature
>          Components: Repository
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Currently, the jcr/webdav module provides WebDAV through the SimpleWebDavServlet in its own servlet context (configurable, default is /dav). This default support requires including the name of the workspace to access in the URL.
> Additional support for WebDAV should be added which allows WebDAV access to the default workspace used by Sling through the Sling Main Servlet. As such, a Sling Servlet is to be registered which implements WebDAV.

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