Filip Hanik - Dev Lists wrote: > Bill Barker wrote: >> <ma...@apache.org> wrote in message >> >> This means that 99% of the time, this valve does nothing (except >> possibly putting bogus values in the log files), since the response is >> already committed. >> > maybe better to implement it as a filter with a response wrapper, that > reacts to setContentType
The wrapper idea would deal with the committed issue. It should also remove the need for the hack I put in the Response. I think I'll stick to a valve rather than a filter as that can be configured at Engine/Host/Context level. A filter is a little less flexible. I'll withdraw the proposal while I work on a better solution. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
