https://bz.apache.org/bugzilla/show_bug.cgi?id=64818
--- Comment #3 from Igal Sapir <isa...@apache.org> --- (In reply to Mark Thomas from comment #2) > I'm leaning towards WONTFIX for this one. > > Given the spec calls this out explicitly as not allowed then I think there > needs to be a very good reason to make an exception and at the moment I > don't see one. But the spec is explicit about duplicate mapping to a different servlet, right? That is not the case here as we're discussing the same servlet. In pseudocode, we're talking about the following: name = "JSP"; name = "JSP"; Is it great and efficient? No. Should it prevent the servlet from launching? IMO, no. (In reply to mgrigorov from comment #1) > Why duplicates should be allowed ? > This is definitely a developer mistake. And it is easy to fix - just remove > the second entry. Agreed on both points, but since this was not expected it took longer to identify the error and correct it. > How such kind of error could go to Production? Does that mean the developer > never started the application locally or at Test/Staging environment ? Ironically all of the initial configurations were tested in Local/Test/Staging environment, but then an urgent issue required adding more mappings and while doing so in "panic" mode, a duplicate entry was added via a copy/paste error which broke the deployment altogether, leading to down time. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
