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: Luke Studley [mailto:[EMAIL PROTECTED]] Sent: 08 December 2001 21:48 To: 'Tomcat Users List' Subject: Filter ResponseWrapper not being called by DefaultServlet Hi I'm attempting to wrap HttpServletResponse in my filter to capture output for XSLT styling. This used to work when I generated the XML out of my own Servlet but now I want to pick it up from a file served by the Default servlet - and my response wrapper is not getting called. I have tried wrapping the request and the response - the request object does seem to be passed into the DefaultServlet - but my response does not! At least the servlet is not calling either getWriter or getOutputStream on my response - but it is writing data to *a* stream as content comes back to the screen. Looking in the DefaultServlet code there doesn't seem to be any reason why it would access any other stream. Anybody have any cluesas to what I am doing wrong. Luke PS Also if I am sending my response wrapper to be called by the default servlet - does my wrapper class have to reside at the same level as the DefaultServlet? Or can it still be used directly from the web application directory? -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
