[
https://issues.apache.org/jira/browse/MTOMCAT-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246314#comment-13246314
]
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: https://issues.apache.org/jira/browse/MTOMCAT-133
> 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 properly.
> 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 :
> https://github.com/hikage/tomcat7-bug
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
