Thanks Tim.
If this is the case I could make it weight-in in the matter of building a
well formed web.xml.
Although it could take some time.
Mapping each servlet to an "/*" url-pattern will avoid us from using invoker
and at the same time get rid of "/servlet" in the URL and keep images under
"/images".
Thanks a lot Tim and thanks to all.
Regards,
Federico.
-----Mensaje original-----
De: Tim Funk [mailto:funk...@apache.org]
Enviado el: miércoles, 08 de junio de 2011 14:53
Para: Tomcat Users List
Asunto: Re: Static resource mapping in web.xml
yes - that would be a problem. The invoker doesn't know how to serve static
resources.
-Tim
On Wed, Jun 8, 2011 at 1:44 PM, <falva...@geocom.com.uy> wrote:
> I agree with you.
>
> The static resources where never a problem to me, but since I messed with
> the web.xml they started to behave oddly.
>
> Maybe this line is causing trouble:
> <servlet-mapping>
> <servlet-name>invoker</servlet-name>
> <url-pattern>/*</url-pattern>
> </servlet-mapping>
>
> It used to be:
> <servlet-mapping>
> <servlet-name>invoker</servlet-name>
> <url-pattern>/servlet/*</url-pattern>
> </servlet-mapping>
>
> What do you think? Can this be interfering with the requests to resources?
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
