http://www.bea.com/ns/weblogic/920/domain
element filter-dispatched-requests-enabled

Model

<filter-dispatched-requests-enabled>boolean</filter-dispatched-requests-enabled>

Disallowed substitutions (block)

none (extensions, restrictions and substitutions are allowed)

Substitution group exclusion (final)

none (extensions and restrictions are allowed)

Usage

Documentation

<p> Indicates whether or not to apply filters to dispatched requests. This
 is a backward compatibility flag. Until version 8.1, WebLogic Server
 applied ServletFilters (if configured for the Web application) on
 request dispatches (and includes/forwards). Servlet 2.4 has introduced the
 "Dispatcher" element to make this behavior explicit. The default value is
 Dispatcher=REQUEST. In order to be complaint with the J2EE specification,
 the default value for FilterDispatchedRequestsEnabled is false beginning with WebLogic
 Server 9.0. Note that if you are using old descriptors (meaning web.xml does
 not have version=2.4), then WebLogic Server automatically uses
 FilterDispatchedRequestsEnabled = true for the Web applications, unless
 filter-dispatched-requests-enabled is explicitly set to false in
 weblogic.xml. This means that old applications will work fine without any
 modification. Additionally, during migration of old domains to the 9.0 domain,
 the migration plugin automatically sets this flag to true. </p>
 (Interface=weblogic.management.configuration.WebAppContainerMBean Attribute=isFilterDispatchedRequestsEnabled)

Fundamental Facets

equality, non-numeric, unbounded, unordered, finit value space

White Space Processing

collapse