Return-Path: 
 <tomcat-dev-return-16400-qmlist-jakarta-archive-tomcat-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org
Received: (qmail 88131 invoked from network); 16 Aug 2002 16:33:47 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 16 Aug 2002 16:33:47 -0000
Received: (qmail 23856 invoked by uid 97); 16 Aug 2002 16:32:43 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org
Received: (qmail 23823 invoked by uid 97); 16 Aug 2002 16:32:42 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-dev-help@jakarta.apache.org>
List-Post: <mailto:tomcat-dev@jakarta.apache.org>
List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org>
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 23716 invoked by uid 98); 16 Aug 2002 16:32:42 -0000
X-Antivirus: nagoya (v4198 created Apr 24 2002)
Subject: Re: [5.0] [PROPOSAL] Refactored mapper
From: Bob Herrmann <bob@jadn.com>
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
In-Reply-To: <3D5C2D70.25A7D5DA@sun.com>
References: 
	<Pine.LNX.4.44.0208151254440.1414-100000@costinm.sfo.covalent.net>
	<3D5C2D70.25A7D5DA@sun.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 
Date: 16 Aug 2002 12:33:42 -0400
Message-Id: <1029515623.3776.61.camel@dhcp-70-230>
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 Thu, 2002-08-15 at 18:38, Patrick Luby wrote:
> Remy and Costin,
> 
> I found the following draft wording that is being considered for the
> Servlet 2.4 spec. The exact wording may change, but the context should
> stay the same. Are there any unimplementable pieces in this proposed
> wording:
> 
> The wording in the 4th paragraph in section 9.10 of the Servlet 2.4 spec
> may change to:
> 
>    The web server must append each welcome file in the order
>    specified in the deployment descriptor to the partial request and
>    check whether a [static] resource [or servlet] in the WAR is
>    mapped to that request URI. The web container must send the
>    request to the first resource in the WAR that matches [in the
>    order of 1. a static resource, 2. a servlet that matches
>    exactly, 3. a servlet that matches according to the path
>    mapping rule].
> 
> Patrick

Humm... how does this help?  

First, note that the "extension mapping" is not mentioned, so things
like *.jsp, *.boo are not relevant to welcome files.  

Consider this,

 <servlet-mapping> 
    <servlet-name>BooServlet</servlet-name> 
    <url-pattern>/boo/*</url-pattern> 
 </servlet-mapping> 

 <servlet-mapping> 
    <servlet-name>FooServlet</servlet-name> 
    <url-pattern>/boo/foo/*</url-pattern> 
 </servlet-mapping> 

 <servlet-mapping> 
    <servlet-name>ExServlet</servlet-name> 
    <url-pattern>exactMatch</url-pattern> 
 </servlet-mapping> 
 
 <welcome-file-list> 
    <welcome-file>index.html</welcome-file> 
    <welcome-file>/boo/AlwaysGoesHere</welcome-file> 
    <welcome-file>/boo/foo/NeverGetsHere</welcome-file> 
    <welcome-file>exactMatch</welcome-file> 
    <welcome-file>index.jsp</welcome-file>  <!-- how come extension
mapping is ok here? or is it not ok. -->
 </welcome-file-list> 
 

Somewhat confused (typical),
Bob


--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>