Return-Path: 
 <tomcat-dev-return-20627-apmail-jakarta-tomcat-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org
Received: (qmail 72645 invoked by uid 500); 2 May 2001 15:13:56 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:tomcat-dev-help@jakarta.apache.org>
list-unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
list-post: <mailto:tomcat-dev@jakarta.apache.org>
Reply-To: tomcat-dev@jakarta.apache.org
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 72352 invoked from network); 2 May 2001 15:13:51 -0000
From: "Philippe Khalife" <pkhalife@dinmar.com>
To: "TOMCAT DEV" <tomcat-dev@jakarta.apache.org>
Subject: TC4 B3: Filters and Load Order bug?
Date: Wed, 2 May 2001 11:13:37 -0400
Message-ID: <CBEFLBDKLLNKGNDNGFIEGEDKCGAA.pkhalife@dinmar.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N


This is a question about Servlet Specification Vs Implementation details.

The filters mappings are applied as per specifications, and in order.

However when initialized by the Container they start by Alphabetical order.
No matter what order I list these filter declarations in, "AuthFilter"
always gets started before "Initalizer", I could rename these but I think it
would be better to have filters initialized in the same order they are
listed, is this a feature that can make it in the next beta? or am  I
missing something?

    <filter>
         <filter-name>Initializer</filter-name>
         <filter-class>core.filter.Initializer</filter-class>
         <init-param>
	 	<param-name>LOG4J_CONFIG_FILE</param-name>
	 	<param-value>/core/config/log4j.properties</param-value>
	 </init-param>
         <init-param>
	 	<param-name>OACONFIG_CONFIG_FILE</param-name>
	 	<param-value>/core/config/oaconfig.properties</param-value>
	 </init-param>
         <init-param>
	 	<param-name>DB_CONFIG_FILE</param-name>
	 	<param-value>/core/config/db.properties</param-value>
	 </init-param>
         <init-param>
	 	<param-name>VELOCITY_CONFIG_FILE</param-name>
	 	<param-value>/core/config/velocity.properties</param-value>
	 </init-param>
    </filter>

    <filter>
        <filter-name>AuthFilter</filter-name>
        <filter-class>cd.filter.AuthFilter</filter-class>
	<init-param>
		<param-name>LOGIN_SCREEN</param-name>
		<param-value>/servlet/core.oas_Login</param-value>
	</init-param>
    </filter>

    <filter>
        <filter-name>AuthFilterStub</filter-name>
        <filter-class>cd.filter.AuthFilterStub</filter-class>
	<init-param>
		<param-name>LOGIN</param-name>
		<param-value>XXXX</param-value>
	</init-param>
	<init-param>
		<param-name>PASSWORD</param-name>
		<param-value>XXXXX</param-value>
	</init-param>
    </filter>




    <filter-mapping>
           <filter-name>Initializer</filter-name>
           <url-pattern>/*</url-pattern>
    </filter-mapping>

    <!-- This is Filter will insert Valid login and password Information
into the session  use it during testing -->
    <filter-mapping>
        <filter-name>AuthFilterStub</filter-name>
	<url-pattern>/servlet/*</url-pattern>
    </filter-mapping>

<!-- Disable this filter during testing, the AuthFilterStub will insert all
User information
    <filter-mapping>
        <filter-name>AuthFilter</filter-name>
	<url-pattern>/servlet/*</url-pattern>
    </filter-mapping>
-->