[ https://issues.apache.org/jira/browse/SLING-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901761#action_12901761 ]
Felix Meschberger commented on SLING-1672: ------------------------------------------ Please also see the discussion at http://markmail.org/message/2nfguno63hq2fvgt. The ultimate point is probably: * The ResourceResolver.listChildren method calls the ResourceProvider.listChildren method of all resource providers registered at or _above_ the location whose children are to be listted * Next the for each ResourceProvider registered _below_ the location whose childre are to be listed a SyntheticResource is created (unless an actual resource exists) for the next segment towards the registered ResourceProvider. Example: Consider three resource providers registered at "/", "/libs", and "/libs/sling/servlet/default". Now we want to list the children of "/libs/sling". - First the listChildren method of the "/" and "/libs" providers are called with the parent path "/libs/sling" - Next for the "/libs/sling/servlet/default" provider a synthetic resource is created for "/libs/sling/servlet" unless this resource has already been returned by one of the other providers. > 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.