Bug 4742 - SPEC - next attribute is not always optional on a step element
SPEC - next attribute is not always optional on a step element
Status: RESOLVED WORKSFORME
Product: jbatch
Classification: Unclassified
Component: source
1
All All
: P5 normal
: ---
Assigned To: cvignola
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-08 20:41 UTC by mminella
Modified: 2013-03-11 14:50 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mminella 2013-03-08 20:41:31 UTC
The next attribute should not be considered optional unless other transitions have been specified (this is not pointed out in 8.2) via their child elements.
Comment 1 cvignola 2013-03-11 14:50:18 UTC
A step is not required to have a transition to another step. Such a step is a final step.  Therefore both the next attribute and the next element are always optional.  Same principle applies to flow, split, and decision.  I agree decision as the final execution element makes little sense.  But we have no reason to prevent it.