One instance of this bean is declared per flow in the request context. The
"invoke action" phase of processing attempts to invoke a method on this bean
named for the "action" method specified in the flow configuration, which is
here decoded and converted into the required method call (or sequence of
calls) on the beans specified in the relevant action states.
These beans are created in FlowProxyFactory, a useful convenience bean that
prevents the user from needing to set the other tedious dependencies of this
bean in addition to the actual target flow object.
Note that this bean causes the FlowIDHolder contents to be set with the
respective flowID if it receives a START transition. This is a somewhat
violation of BeanReasonableness, but we have not yet an architecture for flow
scope construct-time activities.
author: Antranig Basman (antranig@caret.cam.ac.uk) |