Hi, Am Montag, den 31.03.2008, 15:36 +0200 schrieb Vidar Ramdal: > On Mon, Mar 31, 2008 at 3:25 PM, Bertrand Delacretaz > <[EMAIL PROTECTED]> wrote: > > On Mon, Mar 31, 2008 at 3:10 PM, Felix Meschberger <[EMAIL PROTECTED]> > > wrote: > > > > > Am Montag, den 31.03.2008, 14:52 +0200 schrieb Bertrand Delacretaz: > > > > > > > > ...The easiest seems to be for your filter to be declared in > > web.xml.... > > > > >... 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.... > > > > Agreed - I was suggesting a "here and now" solution, but I agree that > > it is not really integrated with Sling. > > OK - how about introducing a new filter.scope - e.g. "prerequest", and > alter SlingMainServlet so that it invokes "prerequest" filters before > passing the request to the ResourceResolver?
Sounds interesting. Such a filter would be defined to get the original request and response objects from the servlet container. That is they would be HttpServletRequest/Response and not SlingHttpServletRequest/Response. Would that suit your needs ? An issue with patch, would of course be very welcome ;-) Regards Felix
