On 10/18/07, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ...we could also drop the SlingRequestPathInfoParser as the (default) > ResourceResolver would by backtracking the path be able to keep track of > the path parts and create a SlingRequestPathInfo object as a byproduct....
I don't like that as the ResourceResolver then does "several things". I prefer keeping a (simple small testable) SlingRequestPathInfoParser to have less coupling. -Bertrand
