tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philippe Khalife" <pkhal...@dinmar.com>
Subject TC4 B3: Filters and Load Order bug?
Date Wed, 02 May 2001 15:13:37 GMT

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>
-->


Mime
View raw message