Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 50087 invoked from network); 24 Aug 2002 21:32:00 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 24 Aug 2002 21:32:00 -0000 Received: (qmail 29440 invoked by uid 97); 24 Aug 2002 21:32:29 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 29406 invoked by uid 97); 24 Aug 2002 21:32:28 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 29394 invoked by uid 98); 24 Aug 2002 21:32:27 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Subject: Re: [5.0] Welcome Files From: Bob Herrmann To: Tomcat Developers List In-Reply-To: <3D679FF5.5000709@apache.org> References: <1029970412.15930.42.camel@dhcp-70-230> <3D679FF5.5000709@apache.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 24 Aug 2002 17:31:57 -0400 Message-Id: <1030224717.24170.223.camel@hue.jadn.com> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sat, 2002-08-24 at 11:02, Remy Maucherat wrote: > Bob Herrmann wrote: > > I have been looking into the Servlet 2.4 section 9.10 Welcome files > > stuff. In a nutshell, the spec now allows servlets to be welcome > > files. The can either be an 'exact match' or a 'prefix match.' > > > > I implemented changes to StandardContextWrapper to bring Tomcat into > > compliance. I think it is pretty messy, but then again Welcome Files > > are messy (per earlier posts.) > > > > What do you think? (The patch is for discussion purposes and contains > > a lot of logging) > > The implementation is not efficient (a simple example: the > getResources() method, which was cut & pasted from DefaultContext > probably, is not appropriate for components which live inside the > container - use Context.getResoruces() instead), but it's not a big deal > as far as I am concerned as I intend to eventually implement a more > efficient mapper. Ok, I will look at switching to use "context.getResources()" on Monday. > > Has the spec wording been fixed ? In short, no. The spec (Proposed Final Draft, Servlet 2.4, Aug 5th 2002) still says, "The [welcome file] match is determined using the usual path mapping rules in Section 11.1." And 11.1 includes the extension mapping rule - and the code I submitted currently ignores that rule. I presume the spec will change with the next update... unless the expert group chooses another solution/change. Cheers, -bob -- To unsubscribe, e-mail: For additional commands, e-mail: