tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <>
Subject RE: valve versus filter
Date Wed, 17 Nov 2004 17:50:45 GMT

Valves have the advantage that you can define them (once) for an entire
Host, so they apply to all the applications on the Host.  However, they
are Tomcat-specific, unlike Filters, so their portability is limited.

The Servlet Spec provides for no way to define a Filter for multiple web
apps.  So any way you choose to proceed will be non-Portable.
Therefore, you might as well stick with your current setup.

Yoav Shapira

>-----Original Message-----
>From: David Boyer []
>Sent: Wednesday, November 17, 2004 12:49 PM
>Subject: Q: valve versus filter
>We're using IIS 6 with the JK2 ISAPI filter (Tomcat 5.0.28).
>I have several filters that I'm using on almost every context in
>production: an authentication filter, an access-control filter, and a
>compression filter. I'd be interested in implementing these things at a
>more global level rather than on a per-context level.
>Would valves be the way to do this? I recognize that valves come into
>the picture at an earlier point in the chain. I'd be interested in
>hearing how other people might approach filters that are being applied
>on all contexts.

This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message