tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gildas Cuisinier (Commented) (JIRA)" <>
Subject [jira] [Commented] (MTOMCAT-133) Servlet mapping to "/" does not work
Date Wed, 04 Apr 2012 14:53:24 GMT


Gildas Cuisinier commented on MTOMCAT-133:

Here is new information to solve this bug:

The code to add mapping :
ServletRegistration.Dynamic myServlet = servletContext.addServlet(//);
Set<String> conflicts = myServlet.addMapping("/");

In Tomcat 7 standalone, the conflits set is empty.
In Maven Tomcat 7 plugin, the conflicts set contains the String "/".

I investigate, and one difference I found is that the "Wrapper" for the jsp servlet and the
default servlet is "overridable" in tomcat 7 but not in maven plugin context.

> Servlet mapping to "/" does not work 
> -------------------------------------
>                 Key: MTOMCAT-133
>                 URL:
>             Project: Apache Tomcat Maven Plugin
>          Issue Type: Bug
>          Components: tomcat7
>    Affects Versions: 2.0
>         Environment: Mac OS X, Apple JRE 1.6
>            Reporter: Gildas Cuisinier
>            Assignee: Olivier Lamy (*$^¨%`£)
> Using the Servlet 3.0 possibilities to add and configure servlet (ServletContainerInitializer
through Spring 3.1 WebApplicationInitializer), I try to map a servlet  "/", but is not working
> The servlet is started correctly, but the mapping does not work. 
> If I replace "/" by "test/*", everything work perfectly.
> For information, the "/" mapping works well in a standalone tomcat 7.0.25.
> I put a sample project on github that reproduce the bug :

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message