Jay Burgess <[EMAIL PROTECTED]> writes: > Didn't we say the same thing? > > I said: "Shouldn't I have gotten an exact match on my web app's default > servlet, instead of it defaulting to Tomcat's default servlet?" > > You said: "But what should happen is that Tomcat uses your servlet > 'myServlet' instead of it's own default servlet." > > Those two statements are equivalent in my mind.
Then you've not understood the subtelties of the spec correctly. The phrase "EXACT MATCH" means something different to matching the default servlet. To be precise, the default servlet is not matched, it is selected when there is no other match. > If so, it sounds like we're both in agreement on this. Maybe a Tomcat'er > will see this over the weekend and comment. I suggest you point out the problem on their mailing list. Make sure that you try the latest version because I'm fairly sure it's been pointed out to them before. > On side note, looking at the Tomcat source, there's an explicit check to > ignore this case in the "exact match" code. I'm confused. Because the default servlet is not an EXACT match. You can see that from the debug that tomcat is producing. Read the spec to find out more about the order and type of matches. Nic ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
