we also found this to be the case when setting up mime types. I think it's
a 'feature' - if you create a new context, only the local web.xml has any
effect.
Rob
pretty
----- Original Message -----
From: "Timothy Shadel" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 15, 2001 8:07 PM
Subject: Default web.xml
> I have a quick question about how the default web.xml found in the conf
directory is supposed to act. The Tomcat User's guide says it acts as a
default web.xml for all web applications. I tried to add the following to
it:
>
> <servlet-mapping> <!-- This was there by default -->
> <servlet-name>
> jsp
> </servlet-name>
> <url-pattern>
> *.jsp
> </url-pattern>
> </servlet-mapping>
> <servlet-mapping> <!-- I added this -->
> <servlet-name>
> jsp
> </servlet-name>
> <url-pattern>
> *.tem
> </url-pattern>
> </servlet-mapping>
>
> because we wanted to logically separate our JSP files used as templates
from those providing major content. However, accessing a valid JSP file
that's been renamed with a .tem extension returns only the actual file
contents instead of being translated as a JSP. The same <servlet-mapping>
tag works perfectly in an application's web.xml. Am I supposed to be able
to modify the web.xml in the conf directory and have it affect all
applications, or is it only supposed to work with the one that comes with
Tomcat by default?
>
> Thanks,
>
> Tim Shadel
>
>
