Thanks so much!!! Works and yeah, forgot to mention that I had defined the Valve at the host level. Again, thanks so much for your fast response.
-----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Monday, October 18, 2004 11:10 PM To: [EMAIL PROTECTED] Subject: Re: tomcat 4.1.30 vs. 5.0.2x In TC 4.1.x, the Context isn't set until you are inside the Context in the pipeline. It will only work on TC 4.1.x if your Valve is defined in the Context. "Monika Koerdt" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Hi - I have the following piece of code running in Tomcat 5.0.2x public class ContextValve extends ValveBase { static ThreadLocal testContext = new ThreadLocal(); public void invoke(Request request, Response response, ValveContext context) throws IOException, ServletException { testContext.set(request.getContext()); context.invokeNext(request, response); } } Seems to work properly on Tomcat 5.0.2x, but when compile it and run it on 4.1.30, the returned context is always null. Any ideas on why this is happening? I just need to get a hold of the context on every request... Thanks, Monika --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
