Konrad Windszus wrote > This is complex to solve for the client (and kind of unexpected that this is > not working). > So what speaks against supporting this use case properly in Sling. > Maybe you can elaborate a bit on >> I think calling resolve() for traversal is totally unexpected. > > IMHO the complex cases should be nicely covered by Sling (instead of adding > that burden to each client). > Of course calling resolve() would only be done for the NonExistingResource > (and maybe the SyntheticResource). The handling for regular existing > resources should stay exactly as is (i.e. not relying on resolve() at all). > > I meanwhile opened https://issues.apache.org/jira/browse/SLING-5773 > <https://issues.apache.org/jira/browse/SLING-5773> about this problem. >
The only place where you get a NonExistingResource is the resolve method, getResource returns null. As this is known, whoever is calling resolve() can check whether the returned resource is a NonExistingResource, then call resolve with the parent path or whatever. What is your use case? Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
