You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Ian Boston <ie...@tfd.co.uk> on 2015/09/07 18:06:05 UTC
Jcr Resource Resolver bundle 2.5, inconsistent Root resource behaviour.
Hi,
If I do [1] with a Jcr Resource Resolver 2.5.0 bundle (AEM6.1) I get
inconsistent results.[2]. Is that fixed in later versions ?
The // is not handled well by some code (VLT DefaultWorkspaceFilter) that
expects well formed paths.
Best Regards
Ian
[1]
Iterator<Resource> i = resourceResolver.getResource("/").listChildren();
while(i.hasNext()) {
LOGGER.info("Child Path {} ",i.next().getPath());
}
[2]
...
//etc
...
/content
...
/libs
...
Re: Jcr Resource Resolver bundle 2.5, inconsistent Root resource behaviour.
Posted by Ian Boston <ie...@tfd.co.uk>.
Hi,
On 8 September 2015 at 12:15, Carsten Ziegeler <cz...@apache.org> wrote:
> Am 08.09.15 um 08:05 schrieb Ian Boston:
> > Hi,
> > https://issues.apache.org/jira/browse/SLING-5005
>
>
> Isn't this SLING-4588 which we fixed for 2.5.2?
>
Yes,
Thank you. That saved me lots of bisecting.
Best Regards
Ian
>
> Carsten
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziegeler@apache.org
>
Re: Jcr Resource Resolver bundle 2.5, inconsistent Root resource
behaviour.
Posted by Carsten Ziegeler <cz...@apache.org>.
Am 08.09.15 um 08:05 schrieb Ian Boston:
> Hi,
> https://issues.apache.org/jira/browse/SLING-5005
Isn't this SLING-4588 which we fixed for 2.5.2?
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org
Re: Jcr Resource Resolver bundle 2.5, inconsistent Root resource behaviour.
Posted by Ian Boston <ie...@tfd.co.uk>.
Hi,
https://issues.apache.org/jira/browse/SLING-5005
I'll take a look today hopefully.
Best Regards
Ian
On 8 September 2015 at 06:30, Antonio Sanso <as...@adobe.com> wrote:
> hi Ian, this looks an issue,
>
> any chance you can track this to a new JIRA :) ?
>
> regards
>
> antonio
>
> On Sep 7, 2015, at 6:06 PM, Ian Boston <ie...@tfd.co.uk> wrote:
>
> > Hi,
> >
> > If I do [1] with a Jcr Resource Resolver 2.5.0 bundle (AEM6.1) I get
> > inconsistent results.[2]. Is that fixed in later versions ?
> >
> > The // is not handled well by some code (VLT DefaultWorkspaceFilter) that
> > expects well formed paths.
> >
> > Best Regards
> > Ian
> >
> > [1]
> > Iterator<Resource> i = resourceResolver.getResource("/").listChildren();
> > while(i.hasNext()) {
> > LOGGER.info("Child Path {} ",i.next().getPath());
> > }
> >
> >
> > [2]
> > ...
> > //etc
> > ...
> > /content
> > ...
> > /libs
> > ...
>
>
Re: Jcr Resource Resolver bundle 2.5, inconsistent Root resource
behaviour.
Posted by Antonio Sanso <as...@adobe.com>.
hi Ian, this looks an issue,
any chance you can track this to a new JIRA :) ?
regards
antonio
On Sep 7, 2015, at 6:06 PM, Ian Boston <ie...@tfd.co.uk> wrote:
> Hi,
>
> If I do [1] with a Jcr Resource Resolver 2.5.0 bundle (AEM6.1) I get
> inconsistent results.[2]. Is that fixed in later versions ?
>
> The // is not handled well by some code (VLT DefaultWorkspaceFilter) that
> expects well formed paths.
>
> Best Regards
> Ian
>
> [1]
> Iterator<Resource> i = resourceResolver.getResource("/").listChildren();
> while(i.hasNext()) {
> LOGGER.info("Child Path {} ",i.next().getPath());
> }
>
>
> [2]
> ...
> //etc
> ...
> /content
> ...
> /libs
> ...