Special filter designed to work with the {@link FilterDispatcher} and allowfor easier integration with SiteMesh. Normally, ordering your filters to have SiteMesh go first, and then {@link FilterDispatcher} go second is perfectly fine.However, sometimes you may wish to access Struts features, including the value stack, from within your SiteMesh decorators. Because {@link FilterDispatcher}cleans up the {@link ActionContext}, your decorator won't have access to the data you want.
By adding this filter, the {@link FilterDispatcher} will know to not clean up andinstead defer cleanup to this filter. The ordering of the filters should then be:
- this filter
- SiteMesh filter
- {@link FilterDispatcher}
@deprecated Since Struts 2.1.3, use {@link org.apache.struts2.dispatcher.ng.filter.StrutsPrepareFilter} and{@link org.apache.struts2.dispatcher.ng.filter.StrutsExecuteFilter} to use other Servlet filters that need access tothe ActionContext
@see FilterDispatcher
@see Dispatcher
@see org.apache.struts2.dispatcher.ng.filter.StrutsPrepareFilter
@see org.apache.struts2.dispatcher.ng.filter.StrutsExecuteFilter
@version $Date$ $Id$