Hi, On 20.08.2010 14:31, Clemens Wyss wrote: >> Hmm, this looks like a strane setup. > no wonder, it's from me ;-) Basically I just wanted a bundle resource (to > test with) and I thought this was simplest way to get one. > >> This header setup is for initial >> content not for bundle resources > the overwrite/uninstall args or the path-redirection? > Again: resolving seems to work, but not enlisting. > >> This might be a bug in the bundle resource provider. > have you got enough info's to track this down?
Yes, but having a JIRA issue would help "not forgetting about it" ;-) Thanks Regards Felix > >> -----Original Message----- >> From: Felix Meschberger [mailto:[email protected]] >> Sent: Friday, August 20, 2010 1:36 PM >> To: [email protected] >> Subject: Re: resource.resourceResolver.listChildren only lists jcr >> nodes? >> >> >> Hi, >> >> >> On 20.08.2010 11:54, Clemens Wyss wrote: >>> in my pom.xml I have: >>> <Sling-Bundle-Resources> >>> >> /res/sling/explorer;overwrite:=true;uninstall=true;path:=/libs >> /sling/explorer >> >> Hmm, this looks like a strane setup. This header setup is for initial >> content not for bundle resources. >> >> But yes, you are right, you should be able to see the "/res" resource >> (synthetic) and then /res/sling, /res/sling/explorer and >> everything below. >> >> This might be a bug in the bundle resource provider. >> >> Regards >> Felix >> >>> </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 >>> >>> now when I enlist on the root (/) I don't see 'res'? Should >> or shouldn't I? >>> >>>> -----Original Message----- >>>> From: Felix Meschberger [mailto:[email protected]] >>>> Sent: Friday, August 20, 2010 11:31 AM >>>> To: [email protected] >>>> Subject: Re: resource.resourceResolver.listChildren only lists jcr >>>> nodes? >>>> >>>> >>>> Hi, >>>> >>>> No, the listChildren method is implemented to return all >>>> child resources >>>> in the Resource tree, not only JCR nodes. >>>> >>>> And no, the ResourceResolver is not specifically wrapped. >>>> >>>> Regards >>>> Felix >>>> >>>> On 20.08.2010 11:20, Clemens Wyss wrote: >>>>> in my esp-script I have the follwoing line: >>>>> >>>>> var childResources = request.resourceResolver.listChildren( >>>> resource ); >>>>> >>>>> To me (having explicitly definde bundle resources) it looks >>>> as if this only lists jcr nodes but not all resources. >>>>> Is this yet another esp limitation (of the wrapper behind >>>> 'resource'), or does listChildren really only return jcr nodes? >>>>> >>>>> Asked the other way round: >>>>> given a path, how do I enlist (in esp) all resources below >>>> that path? >>>> >>
