Jcr Resource Resolver bundle 2.5, inconsistent Root resource behaviour.

[Ian Boston]

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