EscenicStandardFilterChain

The EscenicStandardFilterChain is different from all the other filters specified in WEB.XML. It is not a single filter, but a chain of "subfilters" called processors. Most of the important filter functionality is actually performed by the processors in this chain. The reason that the filters have been packed together like this is as follows:

  • New releases of the Content Store sometimes involve changes to this part of the filter chain, needed to support new functionality.

  • WEB.XML is part of the publication application, not the Content Store.

  • If all the processors were not packed into this single "master filter", then upgrading to new versions of the Content Store would often require customers to make changes to their WEB.XML file(s).

The EscenicStandardFilterChain is configured in WEB.XML as follows:

<filter>
  <filter-name>EscenicStandardFilterChain</filter-name>
  <filter-class>com.escenic.presentation.servlet.CompositeFilter</filter-class>
  <init-param>
    <param-name>oncePerRequest</param-name>
    <param-value>true</param-value>
  </init-param>
  <init-param>
    <param-name>chain</param-name>
    <param-value>/com/escenic/servlet/StandardFilter</param-value>
  </init-param>
</filter>
Configuration
oncePerRequest

If set to true, then the filter is only executed for the initial request. If set to false, then the filter is executed for every request, which on some servers may mean that it is re-applied each time an include operation calls a new JSP file.

chain

The path of the component that manages the chain of processors. There is no default value for this parameter: it must be specified, and should normally be set to /com/escenic/servlet/StandardFilter.

Request Scope Attributes

This filter sets no request scope attributes itself. However, the filter chain processors it executes do set request scope attributes. See the descriptions of the individual processors for details.