Hi Ulrich, On Fri, Jan 25, 2013 at 6:16 PM, Ulrich Schmidt <[email protected]> wrote: > ...So I'm looking for a document, source, ruleset or anything else where I can > extract the way how resolving is done. I found the Interface > "ResourceResolver" > supplied by Sling but have no clue which class is implementing it. Maybe such > a > class would help. I'm astonished anyway, why this interface is mentioned in > all > the websites I found until now instead of the implementing class. As if it was > users responsibilty to do the resolving....
It's not, but IIUC what you want to understand should be split in two things a) Given an incoming request, how does Sling select which Resource to process b) Once that Resource is found, how does Sling select a script or servlet to process the request As Paul indicates, the Sling website does explain those things: a) is mostly explained in http://sling.apache.org/documentation/the-sling-engine/resources.html b) is explained in http://sling.apache.org/documentation/the-sling-engine/servlets.html And useful additional details can be found in the automated tests that these pages point to, and which you might want to expand if you're unsure of something. One useful debugging tool is the "recent requests" OSGi console plugin that you'll find at /system/console/requests in a default Sling setup and is described at http://sling.apache.org/site/monitoring-requests.html As Paul says, CQ5 does add a small layer on top of this, so once you understand the Sling basics you might need to ask on CQ forums for things that are not directly handled by Sling. HTH, -Bertrand
