|
From: Keith D. <ke...@in...> - 2005-03-16 00:33:22
|
Hey guys.
Made some minor tweaks to the web-flow.dtd tonite, adding several new
capabilities:
Below is a purposefully elaborate "action state" definition illustrating the
new stuff:
<action-state id="actionState1">
// execute "action1" when entered, where "action1" is the id of a
selected/exported action impl in the registry (typically a spring bean
factory)
<action id="action1"/>
// execute an instance of the action impl class when entered, impl
instantiated is delegated to registry, no attempt at autowiring
<action
class="org.springframework.web.flow.config.XmlFlowBuilderTests$TestAction"/>
// execute an instance of the action impl class when entered, impl
instantiated is delegated to registry, byType autowire policy
<action
class="org.springframework.web.flow.config.XmlFlowBuilderTests$TestAction"
autowire="byType"/>
// execute an instance of the action impl class when entered, instance
is retrieved from registry by type
<action
classref="org.springframework.web.flow.config.XmlFlowBuilderTests$TestAction
"/>
// on event "event1" transition to "viewState1"
<transition on="event1" to="viewState1"/>
</action-state>
Aside: for those new to web-flow, an action state, when entered, executes
one or more "Action" implementations (kind of like a Controller in terms of
general responsibilities of brokering between the web-tier and middle-tier.)
Look OK?
Keith
|