Correct - the only place the Filter is mentioned is in the web.xml for the "/" Context and the .class file is in that Context.
If it further confirms your understanding, I should mention that in the beginning I *did* have a copy of the Filter under "/hal" (for initial testing of the Filter) and that caused an infinite loop for redirections! The first request to "/" got redirected to "/hal" which then got redirected to "/hal" etc. etc. Chris > Chris, thanks for responding. I think I understand. Sanity > check: the > filter is not even mentioned anywhere in the webapps/hal heirarchy, > right? That hierarchy is totally unaware of the filter. > > If that's the case then all is making sense now. > thanks again, > -joe > > > > Chris Ward wrote: > > >Hi Joe, > > > >I'm not sure exactly what your query is but the setup I have > is a "/" > >and a "/hal" Context. The Filter I am using to direct any > requests to > >"/" to "/hal" lives in the WEB-INF/classes dir of the "/" context. > > > >In my case I used the Tomcat default dir of > "../webapps/ROOT" for the > >"/" docBase. > > > >Further. the configuration for the Filter and the URL > pattern to fire > >it is in the web.xml file in that same WEB-INF dir. I do > use "/*" as > >the URL pattern, but remember that these URL patterbs are relative > >to the Context the web.xml file is in. > > > >i.e. > > > >webapps/ROOT/WEB_INF/web.xml > >URL pattern of "/*" matches http://myserver/* > > > >webapps/hal/WEB_INF/web.xml > >URL pattern of "/*" matches http://myserver/hal/* > > > >Sorry if I've missed your point. > > > >Regards, > >Chris > > > > > > > > > >>Shapira, Yoav wrote: > >> > >> > >> > >>>Howdy, > >>>A javax.servlet.Filter is one nice clean way. > >>> > >>> > >>> > >>> > >>Apologies if this is dumb q: Googling the jakarta site and > >>reading the > >>tomcat o'reilly have left me confused on this. > >> > >>Isn't the filter part of web app? From jakarta: > >> > >> > >> > >>>Filters are configured in the deployment descriptor of a web > >>>application > >>> > >>> > >>And in o'reilly the filter and filter-mappnig tags are > >>discussed in the > >>web.xml section. > >>Doesn't this raise a namespace issue? If your > servlet-mapping is to > >>/foo, then a filter on /* seems like it will either never > >>fire, or else > >>be ambiguous with other /* filters in other web apps (such as > >>the /bar > >>webapp, with it's own /* filter). > >> > >>The original poster had a /hal context and a / context. Does > >>the filter > >>solution require the / context to remain? Or is that unneeded? > >> > >>thanks for any unconfusion, > >>-joe > >> > >> > >> > >> > >> > >>------------------------------------------------------------ > --------- > >>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] > > > > > > > > > > --------------------------------------------------------------------- > 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]
