Summary: | Incorrectly accept many url-pattern on a single servlet-mapping in web.xml | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | Giuseppe Sacco <giuseppe> |
Component: | Unknown | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | 5.5.26 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
Giuseppe Sacco
2012-01-25 21:29:39 UTC
1. Tomcat 5.5 implements Servlet Specification 2.4 [1] The syntax you tried to use was introduced in 2.5. 2. Tomcat 5.5 is near its end of life. New features won't be implemented. 3. Tomcat 7 does validation of web.xml against schema if you enable STRICT_SERVLET_COMPLIANCE mode. [1] http://tomcat.apache.org/whichversion.html Hi Konstantin, thanks for your quick reply. I am unsure about the reason for marking it RESOLVED and INVALID, since I think the problem is still there. Let's recap what you wrote: > 1. Tomcat 5.5 implements Servlet Specification 2.4 [1] > The syntax you tried to use was introduced in 2.5. Ok, this is what I already wrote in my report. > 2. Tomcat 5.5 is near its end of life. New features won't be implemented. This is something new for me. Is there any date for ending support on tomcat 5.5? Is a bugfix really cataloged as "new feature"? > 3. Tomcat 7 does validation of web.xml against schema if you enable > STRICT_SERVLET_COMPLIANCE mode. I don't need web.xml validation, and I am not using tomcat7. So this is useless. If you really think this is a minor bug and do not want to fix it because tomcat 5.5 is not end of life, just mark it as VERIFIED and WONTFIX. Thanks, Giuseppe (In reply to comment #2) > > 2. Tomcat 5.5 is near its end of life. New features won't be implemented. > > This is something new for me. Is there any date for ending support on tomcat > 5.5? It is mentioned in many places. Direct link: http://tomcat.apache.org/tomcat-55-eol.html > Is a bugfix really cataloged as "new feature"? If you deploy a broken web application, the behaviour might be undefined. |