Sometimes, maybe infrequently, there's a decent reason to implement a small amount of code outside of the webapp, in the container space. There are cases where either modifying the webapp is off limits, or where it would simplify things to implement it in container space so that it's just always running, regardless of which webapps are started, stopped, deployed, undeployed, or redeployed. Of course, if Tomcat allowed configuring Filters everywhere it currently allows configuring Valves (as we previously discussed), then these could be implemented as Filters -- right now Valves are the only option for doing this.
-- Jason Brittain On Wed, Sep 30, 2009 at 10:25 AM, shetc <sh...@bellsouth.net> wrote: > > The person paying me :-) > > I suggested a filter but he prefers a valve even though it ties that > functionality to Tomcat. > -- > View this message in context: > http://www.nabble.com/Accessing-a-database-from-a-Valve-tp25673641p25685437.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
