Bugzilla – Bug 4643
OK if flow and split do not contain 'next, stop, end, fail' child elements?
Last modified: 2013-03-20 03:25:49 UTC
Though the RI currently assumes you can do:
(You can see the XSD grants this as a possibility).
I don't see any justification for this in the spec. The spec only seems to grant permission for a split/flow to use the @next attribute on the <flow> or <split> element itself.
So anything more complicated would have to be done in a decision.
This seems like a nice simplification, but I wanted to run it by you before removing this from the RI (and we'll update the XSD as well).
The following elements are meant to be supported as child elements of <flow> and <split>:
This is an error in the spec and will be corrected in PFD v1.5.
We actually went down this path on Bug 4540 and realized a split doesn't get an exit status... so it only makes sense to unconditionally @next from split.
For flow.. if we need a tiebreaker vote on whether to allow this or not.. I will say that the RI/TCK doesn't currently support this (except that I updated the XSD to "support" it).
Only allowing a flow a @next attr puts it more in your face that only a step has exit status.
Flow will support transitions elements. Split will not. The transition elements are stop, end, next, and fail.