Hi, Am Montag, den 31.03.2008, 14:52 +0200 schrieb Bertrand Delacretaz: > On Mon, Mar 31, 2008 at 2:34 PM, Vidar Ramdal <[EMAIL PROTECTED]> wrote: > > > ... So I would like to let the filter process the request before > > SlingMainServlet gets to it. How can I accomplish that (if possible)?... > > The easiest seems to be for your filter to be declared in web.xml. > > I'd suggest first patching the launchpad/webapp web.xml to test your > idea, and if that works you could create your own webapp, either by > overlaying your own web.xml using the maven-war-plugin, or creating a > completely new webapp using the launchpad one as an example.
This is certainly a possibility, but I would not go this route as it leaves Sling and makes it impossible to be used in the standalone launchpad/app case... In addition it is impossible to manage, ie configure and updated the filter. Rather we might want to find a way on how to get this to really influence resource resolution. Given this, it might probably be better enhance the resource resolver to make it extensible in terms of resource resolution. Currently, we have two hard coded resolution steps: vanity urls (just mapping the input path to a nother path) and prefix handling (replacing path prefixes with other prefixes). We might amend this to make these steps optional and extensible ... I could then imagine, that SLING-249 could then be a first use-case. Regards Felix
