This is my concern as well. Our custom login valve is using values from the form authentication valve that are not accessible in the war file. For example they allow reconstruction of a post request and replacing roles and principals, which I doubt can be done with a filter in a simple way without repeating a lot of code. Even though there is a lot in common, I would like to have access to the tomcat internal data and not be limited to the application level API. Valve cam use HttpServletRequest and response, if you know that you can cast them to an internal class with the full API. In that case it may be safer to just use that class in the method signatures.
E ----- Original Message ----- From: Christopher Schultz <ch...@christopherschultz.net> To: Tomcat Users List <users@tomcat.apache.org> Sent: Wed, 21 Oct 2009 08:11:17 -0700 (PDT) Subject: Re: Valves being converted to Filters? Will there be a way to grab information from the "raw" request as seen by a Valve today? It's nice to be able to get and set values "above" (or below, depending on your POV) the servlet API. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
