A Valve is just like a Servlet Filter but tomcat specific. They are run early
enough in the request lifecycle that you can change different behaviors of
how things work. But a Valve also has access to tomcat's internals, something
servlet filters don't have.
http://jakarta.apache.org/tomcat/tom
te from Servlet Spec mandates on session tracking, but I
imagine you already know that and have no choice.
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Markus Krogemann [mailto:[EMAIL PROTECTED]
Sent: Friday, September 17, 2004 8:32 AM
To: Tomcat Users List
Subjec
More a question than an answer: Could a servlet filter do the job?
Markus Krogemann <[EMAIL PROTECTED]> schrieb am
17.09.2004, 14:31:51:
> Dear List,
>
> I am having a hard time to figure out how I could fulfill a special
> requirement in a current project.
>
> I could use either tomcat 4.1.x
I think you might need to use a Valve instead of Http...Wrapper. The
Http...Wrappers can't dig enough into the correct internals to do your
session management. But the Valves (probably) can. (Without me thinking about
the details)
With a valve you should be able to wrap or change the internal t
tracking, but I
imagine you already know that and have no choice.
Yoav Shapira
Millennium Research Informatics
>-Original Message-
>From: Markus Krogemann [mailto:[EMAIL PROTECTED]
>Sent: Friday, September 17, 2004 8:32 AM
>To: Tomcat Users List
>Subject: Using custom
Dear List,
I am having a hard time to figure out how I could fulfill a special
requirement in a current project.
I could use either tomcat 4.1.x or tomcat 5.0.x for this project, I
presume it doesn't make much difference in terms of possible solutions.
The project also uses struts (1.2.2) and he
