users@glassfish.java.net

Servlet filter difference...

From: vince kraemer <Vince.Kraemer_at_Sun.COM>
Date: Sun, 20 Jul 2008 16:02:09 -0700

Hi,

I have a question about differences between GF V2 and Tomcat 6,
regarding servlet filters...

I have a servlet filter that I configure into the default-web.xml for
GlassFish. I deploy a web app to GF... My filter's code executes. That
is a good thing. I remove the info about the filter from the
default-web.xml and restart GF V2. My filter's code still gets
executed... Not quite what I wanted.

To make sure that the filter is not going to execute, I have to redeploy
any and all apps that I deployed while the filter was defined in
default-web.xml...

If I manipulate the "default" web.xml for Tomcat 6, the filter stops
getting called after I remove the reference to it and restart...

Is there a way to get GF to behave like Tomcat? I really don't want to
redeploy all my apps after removing the reference to the filter from the
default-web.xml...

Is there a different place that I could put this "default filter" info
that would be more likely to behave like Tomcat?

How about in V3?

Thanks,
vbk