https://bz.apache.org/bugzilla/show_bug.cgi?id=64818
--- Comment #9 from Igal Sapir <isa...@apache.org> --- (In reply to Mark Thomas from comment #4) > <snip/> > > I've traced this back to the original EG discussion and it was only > considering one URL pattern mapping to multiple Servlets. The case of > duplicate mappings (same URL, same servlet) was not discussed. > > While I accept that the spec language is not as explicit as I thought, I > remain of the view that this should be a WONTFIX. If this situation arises, > clearly an error has occurred. The proposed solution assumes one particular > error and "auto-corrects" based on that assumption. However, the assumption > may not be valid. I think it is better to fail the deployment and require > the error to be fixed rather than making assumptions about how it should be > fixed. The assumption may or may not be valid, but I still think that it's harsh to fail the deployment over a no-op config element. We can always print a warning to the log or stderr. (In reply to Mark Thomas from comment #8) > Moving to enhancement. Does the move to enhancement mean anything (e.g. that it's OK to implement)? If so then I'd be happy to patch it, but if there's still a strong objection then let's close the ticket so that we don't spend more time on it. -- 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
