RE: Are filters restricted to be within contexts?

[Peter Crowther]

 From: David Kerber [mailto:[EMAIL PROTECTED] 
 Basically, I'd like to know if a filter can be used to change 
 a context 
 path, or are they restricted to acting within a given context?

Filters are spec-compliant and per-context.  Valves are Tomcat-specific
and can be per-instance.  You could probably get the effect you want
with a valve - give us more information and you might get more specific
pointers :-).

- Peter

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Are filters restricted to be within contexts?

[David Kerber]

Thanks for the quick resopnse, Peter -

This goes back to questions I've been asking for a few weeks here, 
trying to get something going whereby I can make my context paths 
non-case-sensitive.  After playing with filters, I finally figured out 
that I could not get them to work outside of a context.  So I was 
wondering if that was an inherent characteristic of filters, which it 
apparently is. 

Then I got to thniking that if there was a way of trapping invalid 
context paths, I could check to see if the invalid context was just a 
different case of a valid one, and if so, I could just correct the 
path or forward the request to the correct context.  I've been told I 
can do this with Apache HTTPD, but didn't want to have to install that 
just to get this bit of added functionality.


Does that sound doable?
Dave


Peter Crowther wrote:

From: David Kerber [mailto:[EMAIL PROTECTED] 
Basically, I'd like to know if a filter can be used to change 
a context 
path, or are they restricted to acting within a given context?
   



Filters are spec-compliant and per-context.  Valves are Tomcat-specific
and can be per-instance.  You could probably get the effect you want
with a valve - give us more information and you might get more specific
pointers :-).

- Peter

-
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]

Re: Are filters restricted to be within contexts?

[David Smith]

Any request not matching a specific webapp's path belongs to the ROOT
webapp.  Place filters there if you'd like to catch requests to
non-existent webapps.  Otherwise if a request matches a webapp, that
webapp's filters are run instead.

--David

David Kerber wrote:

 Basically, I'd like to know if a filter can be used to change a
 context path, or are they restricted to acting within a given context?

 For example, can I set up a filter at a higher level, so that it will
 trigger even on a context that doesn't exist in the current Tomcat
 instance?


 Thanks!
 Dave



 -
 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]