On Fri, 16 Aug 2002, Patrick Luby wrote: > I really don't like this spec change either. After carefully reading the > revised wording, it still seems that spec is saying "if I can't find any > of the listed static welcome files, start looking for anything that can > serve up a response". > > OK, maybe I am being overly dramatic, but it seems that the spec is > trying to apply complex pattern matching rules to when the user requests > the "/" resource and the webapp is missing all of the static welcome > file resources. As far as I can tell, the only time the servlet mapping > gets used is when the webapp has, for example "/index.html" as a welcome > file and then then the webapp developer forget to put a "index.html" > file in the webapp.
Or index.jsp ? If index.jsp has been precompiled - you need path mapping. What if you have struts and index.do ? With no real file in the dir, but some definition in an xml file ? > Am I missing some bigger and better feature? Or is this spec trying to > solve a problem that can be easily handled with the existing welcome > file behavior? There is no 'existing welcome file behavior' in the servlet spec. The spec has allways been broken, and people just ignored it and implemented what the web servers are doing and users expect. The root of the problem is the extension mapping definition that can't check for existence of the resource ( since the resource is no longer there ). You either exclude extension mapping, or allow only 'normal' extension mapping ( the one used by web servers ). Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
