[
https://issues.apache.org/jira/browse/SLING-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903793#action_12903793
]
Felix Meschberger commented on SLING-1672:
------------------------------------------
I have implemented a prototype in my workspace which is functional. Thus taking
over and scheduling for the next release.
> 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: Felix Meschberger
> Fix For: JCR Resource 2.0.8
>
>
> 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.
