> I agree the API is bad in the end, you don't really know which context is > being returned. For example if the context you're requesting is not > deployed, you'll get the root context and a random error when using it.
I'm confused about why people think this behavior is random. It is not the API's job to protect against mis-configuration. The API itself should be predictable. If you request the context for a uri and the desired context isn't deployed, you will either get null if there is no ROOT context deployed or you will get the root context. If you get the root context and the resource you are looking for is not there, you will get a predictable error when you try to dispatch a forward or include. And it will be a configuration problem that can be easily diagnosed. "Oh, my log file says it failed to include /mysite/templates/defaulttemplate.jsp. I must not have mysite.war deployed." If we agree that the spec allows for (not requires, just allows for) stem matching, then the way it worked previously is the exact way that it should work. Again, it is the way that every other commonly used servlet container interprets the spec. Kind regards, Doug --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
