On Wed, Sep 23, 2009 at 1:22 PM, Ian Boston <[email protected]> wrote: > ...What I don't see justification for, is parsing the path into selectors, > extensions etc when we have no evidence what is the right parsing. > The patch adopts a convention as justification for the parsing but IIUC that > convention hasn't been adopted in a,b or c1...
I agree that hardcoding this parsing in the api bundle feels weird. If we want to avoid that, the changes should go into JcrResourceResolver2 instead, where the NonExistingResource is created. The parsing can then use a configurable regexp (or a service? we probably don't need to go that far) to extract the resource path from the request path. -Bertrand
