Requests are managed by and delegated to a FlowExecutor , which this
class delegates to using a FlowRequestHandler (allowing reuse of
common front flow controller logic in other environments). Consult the
JavaDoc of those classes for more information on how requests are processed.
On each request received by this action, a StrutsExternalContext
object is created as input to the web flow system. This external source event
provides access to the action form, action mapping, and other struts-specific
This class also is aware of the SpringBindingActionForm adapter,
which adapts Spring's data binding infrastructure (based on POJO binding, a
standard Errors interface, and property editor type conversion) to the Struts
action form model. This option gives backend web-tier developers full support
for POJO-based binding with minimal hassel, while still providing consistency
to view developers who already have a lot of experience with Struts for
markup and request dispatching.
Below is an example struts-config.xml configuration for a
Other notes regarding Struts/Spring Web Flow integration:
The benefits here are substantial: developers now have a powerful web flow
capability integrated with Struts, with a consistent-approach to POJO-based
binding and validation that addresses the proliferation of
ActionForm classes found in traditional Struts-based apps.