Return-Path: 
 <tomcat-dev-return-16403-qmlist-jakarta-archive-tomcat-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org
Received: (qmail 2361 invoked from network); 16 Aug 2002 16:46:32 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 16 Aug 2002 16:46:32 -0000
Received: (qmail 28635 invoked by uid 97); 16 Aug 2002 16:46:38 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org
Received: (qmail 28585 invoked by uid 97); 16 Aug 2002 16:46:34 -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 28525 invoked by uid 98); 16 Aug 2002 16:46:32 -0000
X-Antivirus: nagoya (v4198 created Apr 24 2002)
Message-ID: <3D5D2C45.3090701@apache.org>
Date: Fri, 16 Aug 2002 18:45:57 +0200
From: Remy Maucherat <remm@apache.org>
Organization: ASF
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.1b) Gecko/20020721
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: Re: [5.0] [PROPOSAL] Refactored mapper
References: <Pine.LNX.4.44.0208151254440.1414-100000@costinm.sfo.covalent.net>
 	<3D5C2D70.25A7D5DA@sun.com> <1029515623.3776.61.camel@dhcp-70-230>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Bob Herrmann wrote:
> 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),

And imagine what users will say ;-)

Basically, I read it as not using extension mapping for non physical 
resources, but only for physical resources (otherwise the default home 
page of Tomcat when you set it up won't work, which is a problem IMO ;-)).

It now looks doable with the standalone Tomcat. It may still be 
unimplementable through Apache, though.

My wish would be that only physical resources can be used as welcome 
files, so that the spec is implementable through a native webserver.
(Quite frankly, the use case for the rest is very limited, and very 
confusing; plus it would impose a complex wording in the spec - still 
not right in that version)

Remy


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