|
From: Serge B. <ser...@gm...> - 2006-04-07 13:14:53
|
Sorry, the letter has flown away.
And now a short example (this is just a general model):
A-flow.xml:
<flow start-state=3D"start">
<decision-state id=3D"start">
<!-- ... -->
</decision-state>
<view-state id=3D"view" view=3D"A"/>
<import resource=3D"common-flow-beans.xml" />
</flow>
B-flow.xml:
<flow parent-flow=3D"start">
<view-state id=3D"view" view=3D"B"/>
</flow>
So, I am implying, that the flow "B" will inherit all states and beans of
the flow "A" and in flow "B" we can redefine some states to change the flow
behaviour.
I want to define some generic flow and then create inherited flows. (At the
same we define beans in application context) I can suppose that abstract
abstract flow and abstract flow state will be useful for building inherited
flows:
<flow abstract=3D"true"...
<view-state id=3D"view" abstract=3D"true"...
e Bogatyrjov <ser...@gm...>:
>
> Hi,
>
> The subject is self-explanatory. I am thinking this feature will be very
> useful. Example:
> A-flow.xml:
>
> <flow start-state=3D"start">
>
>
>
|