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

Felix Meschberger commented on SLING-1672:
------------------------------------------

Rev. 990628: Created a new ResourceIterator class from the internal class of 
the ResourceProviderEntry.listChildren method. This class is now directly 
created from the JcrResourceResolver.listChildren method. The 
ResourceProviderEntry.listChildren method is removed.

Adapted the Servlet Resolver ResourceProvider implementation in Rev. 990629 to 
not generate the synthetic resource iterator entries for the 
ResourceResovler.listChildren method any more because this is now done by the 
JcrResourceResolver.

> 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.

Reply via email to