[
https://issues.apache.org/jira/browse/SLING-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900745#action_12900745
]
Justin Edelson commented on SLING-1672:
---------------------------------------
This is trickier than I thought...
The BundleResourceProvider provides resources starting with the path in the
manifest.
I'm not sure that the BundleResourceProvider should be *providing* the "/res"
resource in this case.
There was an issue with listing the contents of a mapped path (SLING-1674)
which I found while looking into this, but that's not the issue here. This
issue is that the resource provider doesn't provide resources which don't start
with "/res/sling/explorer" and that seems to be to be the correct behavior.
> resource.resourceResolver.listChildren only enlists jcr nodes but not all
> child resources
> -----------------------------------------------------------------------------------------
>
> Key: SLING-1672
> URL: https://issues.apache.org/jira/browse/SLING-1672
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Environment: sling from trunk (as of August 20th 2010)
> Reporter: Clemens Wyss
> Assignee: Justin Edelson
>
> in my esp-script I have the follwoing line:
> var childResources = request.resourceResolver.listChildren(resource );
> In my pom.xml I have the follwoing declaration:
> <Sling-Bundle-Resources>
>
> /res/sling/explorer;overwrite:=true;uninstall=true;path:=/libs/sling/explorer
> </Sling-Bundle-Resources>
> i.e. I map /res/sling/explorer to /libs/sling/explorer. And I can directly
> access the files beneath /res/sling/explorer, e.g.
> http://localhost:8080/res/sling/explorer/css/explorer.css. I.e. resolving
> seems to work
> But when I enlist (which end up in BundleResourceProvider#listChildren()) on
> the root (/) I don't see 'res'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
