Bug 4643 - OK if flow and split do not contain 'next, stop, end, fail' child elements?
OK if flow and split do not contain 'next, stop, end, fail' child elements?
Product: jbatch
Classification: Unclassified
Component: source
PC Windows
: P5 enhancement
: ---
Assigned To: cvignola
Depends on:
  Show dependency treegraph
Reported: 2013-02-05 17:06 UTC by ScottKurz
Modified: 2013-03-20 03:25 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description ScottKurz 2013-02-05 17:06:17 UTC
Though the RI currently assumes you can do:

<flow >
  <next on=
  <end on="

(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).
Comment 1 cvignola 2013-03-01 13:36:25 UTC
The following elements are meant to be supported as child elements of <flow> and <split>:

1. <end>
2. <stop>
3. <next>
4. <fail>

This is an error in the spec and will be corrected in PFD v1.5.
Comment 2 ScottKurz 2013-03-15 19:12:12 UTC

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.
Comment 3 cvignola 2013-03-20 03:25:49 UTC

Flow will support transitions elements.  Split will not.  The transition elements are stop, end, next, and fail.