On 3/1/07, Adam Lally <[EMAIL PROTECTED]> wrote:
While we're on that topic, since I added a ParallelStep that the Flow Controller can return, I wonder if we also want to extend <fixedFlow> to allow including a parallel step. So something like: <fixedFlow> <node errorAction="continue" >ae1</node> <parallel> <node errorAction="terminate">ae2</node> <node errorAction="continue">ae3</node> </parallel> </fixedFlow>If we don't do this then people who want to configure a parallel flow would need a custom flow controller, which seems a little bit like overkill. A concern is that we'd be adding complexity to what used to be a very simple concept for the <fixedFlow>, but I think we can hide this from most users until they start to care about more complex flow options.
On second thought it may be messy to try to extend the Java interface for FixedFlow while keeping it backwards compatible (it has a getFixedFlow() method that returns a String array, currently). We could add another built-in flow type that allows the errorAction/continueOnError flag as well as parallel steps. But what to call it? complexFlow? -Adam
