On Mon, Jul 6, 2009 at 6:20 PM, Tobias Bocanegra<tri...@day.com> wrote: > if the selectors 'catch' they should not be included in the path. > rather assume a non-existing resource > at /content/some/path/foo. the script can still assemble the full path > by concatenating all selectors and extensions. > > is there a reason why using the full path ?
The reason was backwards compatibility: existing serlvets registered for nonexistent resources would use the path (and obviously ignore the rest of the path info, since it's always empty). Not changing that would keep them working. Note that this case is distinctively marked: through the sling:nonexistent resource type (and all the other differences that come up when a resource does not exist yet). Therefore a special handling is IMHO ok. Regards, Alex -- Alexander Klimetschek alexander.klimetsc...@day.com
