[
http://issues.apache.org/jira/browse/JCR-276?page=comments#action_12358894 ]
angela commented on JCR-276:
----------------------------
discussion of variants:
1) redirection to the default-workspace
-----------------------------------------------------------------------------------------------------
when accessing the not-existing root collection -> login with 'null' workspace
and redirect to resource representing the repository root-node, thus
including the workspace name obtained from the session.
-> my favorite solution. but windows builtin dav client does not respect
redirects. therefore dropped.
2) build a fake-root resource
------------------------------------------------------------------------------------------------------
resource with no representation in the repository. none of the write or
lock methods would be allowed. it would only serve as collection for
all the available workspaces.
-> separate resource implementation needed (see also jcr package)
-> need to make sure, that the new Repository-login is issued when the
user accesses any of the workspace resources (and its members)
-> perhaps confusing if the root does not allow any write operation?
would be an option but i'm not sure, whether its really favorable....
3) don't allow connection without valid resource-locator
-------------------------------------------------------------------------------------------------------
perform Repository.login with 'null' workspace in case the locator obtained from
the dav-request does not provide workspace information (e.g. when
using the simple-resourcelocator) of if the workspace is "".
validation check however is delegated to the resource implementation
itself -> thus throwing 404 if the locator is null or does not provide a
resourcepath.
consequence:
when using webdav/jcr/DavLocatorFactoryImpl accessing the 'root-collection'
(thus connecting without valid workspace name) is not possible.
switching back to the factory implementation in webdav/simple allows
connection without workspace name.
> SimpleWebdavServlet: avoid 404 for the root collection
> ------------------------------------------------------
>
> Key: JCR-276
> URL: http://issues.apache.org/jira/browse/JCR-276
> Project: Jackrabbit
> Type: Improvement
> Reporter: angela
> Assignee: angela
> Priority: Minor
>
> in order to avoid strange 404 error when accessing the root collection in
> simple webdav servlet (thus missing workspace name), that request should
> either be redirected or handled by a create fake root that has no
> correspondance in the jsr170 repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
