|
From: Keith D. <ke...@in...> - 2005-03-16 12:50:31
|
>Is the ''transition on=...' just a direct replacement for 'transition
event=...'?
Yes, do you like that better? I think it reads cleaner: e.g on the
occurrence of this, do that. I tried "on-event" as well, but thought it to
be verbose.
Keith
_____
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
David Hewitt
Sent: Wednesday, March 16, 2005 5:54 AM
To: spr...@li...
Subject: RE: [Springframework-developer] spring web flow dtd additions
Keith,
I like the convenience of the terser definition of actions - it avoids the
glut of action definitions that end up in the application context, and
having to skip from the webflow definition to the app context to see what's
going on. I have wanted to be able to do exactly this a number of times.
Is the ''transition on=...' just a direct replacement for 'transition
event=...'?
-Dave
_____
From: spr...@li... on behalf of
Keith Donald
Sent: Wed 16/03/2005 00:32
To: spr...@li...
Subject: [Springframework-developer] spring web flow dtd additions
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
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
|