RE: Filter ResponseWrapper not being called by DefaultServlet

Also if I use a named dispatcher to call the DefaultServlet it does not use the HttpServletResponse object I send it. Surely this is wrong?! Anybody else find this behaviour? Anybody else successfully place response filters on static resources? Regards Luke -Original Message- From:

Re: Filter-Tag Problems with TC 4.0.1

You have to follow the exact order as specified in the DTD. The xml parser is picky on this point. Check the DTD and your web.xml file to make sure there aren't any elements before that should be after and so forth. --David On Wednesday 05 December 2001 05:53 pm, you wrote: Hi everyone,

Re: filter applied on JSP?

Use the url-pattern element instead of the servlet-name element and you're good to go filter-mapping filter-nameservletLogFilter/filter-name url-pattern index.jsp /url-pattern /filter-mapping k At 11:15 AM 11/12/01 -0700, you wrote: is it possible to have a filter working on a JSP

Re: filter mapping

On Tue, 14 Aug 2001, Lin, Zhongwu wrote: In tomcat 4.0, how do I map filter ( my filter ) to servlet my simple servlet ? You can map a filter either by servlet-name or by url-pattern. Given the servlet definition you have below, your first option should be correct. So what request URI

Re: Filter

Fernando Padilla wrote: I am unknowledgable to the Servlet 2.3 specification, so I would like pointers to using Tomcat with "Filter"s. If it is as simple as go read the spec, then just ignore this. Reading the spec (and the associated API docs) is a good starting point. You can get it at:

<    1   2