Hi Konrad, On Mon, Sep 19, 2016 at 11:37 AM, Konrad Windszus <konra...@gmx.de> wrote: > ...So basically we have to distinguish between existing and non existing > resource paths...
Even if someone knew these details off the top of their head (which I don't) IMO the only sane way to document these things in a foolproof way is with automated tests. Keep the docs at the overview / basic principles level, and put the Whole Truth in readable tests. I think the script resolution page [1], which points to the ScriptSelectionTest [2] is a good example of that, that we might want to replicate for the URL decomposition components. -Bertrand [1] https://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html [2] http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/resolver/src/test/java/org/apache/sling/servlets/resolver/internal/helper/ScriptSelectionTest.java
