I will reply to myself since I have worked out the solution and other might find it useful
Valve itself must go in <tomcat>/server Supporting code for valve and classes exposed to the jsp must go in <tomcat>/common -----Original Message----- From: Paul Moore [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 11, 2005 1:32 PM To: tomcat-dev@jakarta.apache.org Subject: communication from jsp to valve I have a valve that does various valve type things, mess with requests, twiddle cookies, etc. I need a JSP to be able to communicate with the valve (generate URLS based on the result of some of the twiddling for example). The class loaders are doing their best to stonewall me. I have tried putting my TwiddlyValveInterface instance in A) thread locals - get null out (different ThreadLocal class with different static map?) B) appContext attribute - class cast error (clear sign that I loaded through different loaders) What is the recommended way to do this? --------------------------------------------------------------------- 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]
