I forgot to mention - my web.xml is in  mywebapp/WEB-INF/web.xml


---------------------------------------- Message History 
----------------------------------------


From: Kitching Simon <[EMAIL PROTECTED]> on 15/01/2001 17:58 CET

Please respond to [EMAIL PROTECTED]

To:   "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject:  RE: <url-pattern> mapping worked in 3.1, but not 3.2.1


$TOMCAT_HOME/conf/web.xml is not used in tomcat 3.2

Put the mapping in yourwebapp/WEB-INF/web.xml

> -----Original Message-----
> From:   David Fan [SMTP:[EMAIL PROTECTED]]
> Sent:   Monday, January 15, 2001 5:51 PM
> To:     [EMAIL PROTECTED]
> Subject:     <url-pattern> mapping worked in 3.1, but not 3.2.1
> Importance:  High
>
>
> Hi,
>
> I have the following configuration in my web.xml which used to work in
> tomcat 3.1:-
>
>     <servlet>
>       <servlet-name>app</servlet-name>
>       <servlet-class>abc</servlet-class>
>     </servlet>
>     <servlet-mapping>
>         <servlet-name>
>           app
>      </servlet-name>
>         <url-pattern>
>           /app/*
>      </url-pattern>
>     </servlet-mapping>
>
> When I upgraded to tomcat 3.2.1, the mapping does not work anymore.  I
> used to be able to map http://server/mywebapp/app/xxx.html to my servlet
> 'abc'.
> Since the upgrade, tomcat does not seem to know about anything from
> http://server/mywebapp/app or below (e.g.
> http://server/mywebapp/app/xxx.html) -
> at least as far as I can see from the log file when the debug level in
> 'mywebapp' context has been set to 13.
>
> The following still works with the above setting (as one would expect): -
> http://server/mywebapp/servlet/app
> http://server/mywebapp/servlet/abc
>
> However, it is not very satisfactory as the above still expose 'servlet'
> in the URL path.
>
> The evidence so far led me to believe something has been changed on the
> interpretation of the <url-pattern> tag.  Has anyone experience similar
> problem,
> and how can this be solved?
>
> Thanks in advance.
>
> David
>
>
>
> --
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorised copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]

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






--

This e-mail may contain confidential and/or privileged information. If you are not the 
intended recipient (or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail. Any unauthorised copying, disclosure or 
distribution of the material in this e-mail is strictly forbidden.


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

Reply via email to