Re: Question about xml workflow descriptor
"Pat Lightbody" <[email protected]>
| Newsgroups | gmane.comp.java.open-symphony.devel |
|---|---|
| Message-ID | <053f01c315c7$841e7690$6901a8c0@moose> |
> 1. It looks like a split defines many unconditional results, but a regular > action can only have one unconditional result and many conditional results. > What was the reasoning behind this... i.e. do you only use splits if you > have 2 unconditional results and actions if you have 1 unconditional and say > 3 conditional results? If so, why wouldn't you just use a split to define > the 1 unconditional and 3 conditional results? I'm just trying to understand > the difference between the two A split actually causes the process to split off in to two or more distinct paths, while a norml action can have only one path it continues down (that path can depend on conditions, however). Hope that helps. > 2. If you perform a split at some point, do they have to come back together > into a join later on in the workflow? (I'd think not, but I'm not exactly > sure) Nope. -Pat ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com