You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Mikołaj Mański (JIRA)" <ji...@apache.org> on 2015/11/13 16:23:11 UTC

[jira] [Commented] (SLING-5219) Mounting a ResourceProvider makes it impossible to create child resources under it

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

Mikołaj Mański commented on SLING-5219:
---------------------------------------

I think this issue is slightly more complicated. We cannot create new resources under existing FsResource as it's provider is not modifiable (FsResourceProvider doesn't implement ModifyingResourceProvider). Decision should be made on whether we should support creating child resources under FsResource at all, and if yes - which way is the best. As it lies under concrete file system path and handles files/directories only, should we create file/directory under FS provider?

> Mounting a ResourceProvider makes it impossible to create child resources under it
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-5219
>                 URL: https://issues.apache.org/jira/browse/SLING-5219
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: Servlets Post 2.3.6
>            Reporter: Robert Munteanu
>
> (I am not sure where the problem is exactly, but setting it under Servlets POST for now ).
> Consider the following scenario:
> * JCR provider mounted at {{/}}
> * FS provider mounted at {{/content/blog/images}}
> * No resources in the JCR repo for {{/content}} or {{/content/blog}}
> A POST call to create {{/content}} or {{/content/blog}} ( I have used [httpie|https://github.com/jkbrzt/httpie] )  fails {noformat}http --auth=admin:admin -f POST http://localhost:8080 /content 'sling\:target=/content/blog/posts'{noformat}
> If I remove the FS provider then the call succeeds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)