Page History

...

The framework stores all its value stack information as request attributes, meaning that if you wish to display data that is on the stack (or even the ActionContext), you can do so by using the normal tag libraries that come with the framework. That's it!

ActionContextCleanUp

Under the framework's Architecture, the standard filter-chain optionally starts with the ActionContextCleanUp filter, followed by other desired filters. Lastly, the FilterDispatcher handles the request, usually passing it on to the ActionMapper. The primary purpose of the ActionContextCleanUp is to provide SiteMesh integration. The clean-up filter tells the dispatcher filter exactly when to remove obsolete objects from the request. Otherwise, the ActionContext may be removed before the decorator attempts to access it.

...

{snippet:id=description|javadoc=true|url=org.apache.struts2.dispatcher.ActionContextCleanUp}

FreeMarker and Velocity Decorators

The framework provides an extension of the SiteMesh PageFilter to assist with integration with Velocity and FreeMarker. Our filters provide the standard variables and Struts Tags that you used to create views in your favorite template language.

FreeMarker

The FreeMarkerPageFilter extends the SiteMes PageFilter to allow direct access to framework variables such as $stack and $request.

...

{snippet:id=example.freemarker.filter.chain|javadoc=false|lang=xml|url=struts2/apps/showcase/src/main/webapp/WEB-INF/web.xml}

{snippet:id=javadoc|javadoc=true|url=org.apache.struts2.sitemesh.FreeMarkerPageFilter}

Velocity

The VelocityPageFilter extends the SiteMesh PageFilter to allow direct access to framework variables such as $stack and $request.

...