diff --git a/docs/src/site/docbook/reference/step.xml b/docs/src/site/docbook/reference/step.xml index c1d61cf5a..2f297b0f4 100644 --- a/docs/src/site/docbook/reference/step.xml +++ b/docs/src/site/docbook/reference/step.xml @@ -1014,7 +1014,7 @@ configuration will always be the first step executed by the Job. The order of the other step elements does not matter, but the first step must always appear - first in the xml. + first in the xml. @@ -1064,7 +1064,7 @@ cannot have both a "next" attribute and a transtion element. The next element specifies a pattern to match and the step to - execute next: + execute next: <job id="job"> @@ -1302,7 +1302,7 @@ ExitStatus of "EARLY TERMINATION" and step3 will not execute; otherwise, execution will move to step3. Additionally, if step2 fails, and the Job is - restarted, the execution will begin again on step2. + restarted, then execution will begin again on step2. <step name="step1" next="step2"> <step name="step2"> @@ -1317,24 +1317,20 @@ The 'pause' element instructs a Job to stop with a BatchStatus of STOPPED. Pausing a - Job is a meant to be a temporary so that the - operator can take some action before restarting the - Job. The 'pause' element requires a 'to' + Job is a meant to be a temporary break in + processing so that the operator can take some action before restarting + the Job. The 'pause' element requires a 'to' attribute that specifies the step where execution should pick up once - the Job is restarted after being paused. + the Job. - In the following scenario, step1 will execute and COMPLETE. The - job will then stop. Once it is restarted, execution will begin on + In the following scenario, if step1 finsihes with COMPLETE, then + the job will then stop. Once it is restarted, execution will begin on step2. <step name="step1"> - <stop on="COMPLETED" to="step2"/> + <pause on="COMPLETED" to="step2"/> </step> - <step name="step2"> - <next on="FOO" to="step3"/> - <end on="*" status="FAILED"/> - </step> - <step name="step3" /> + <step name="step2"/> @@ -1383,6 +1379,32 @@ + +
+ Split Flows + + Every scenario described so far has involved a + Job that executes its + Steps one at a time in a linear fashion. In + addition to this typical style, the Spring Batch namespace also allows + for a job to be configured with parallel flows using the 'split' + element. As is seen below, the 'split' element contains one or more + 'flow' elements, where entire separate flows can be defined. A 'split' + element may also contain any of the previously discussed transition + elements such as the 'next' attribute or the 'next', 'end', 'fail', or + 'pause' elements. + + <split id="split1" next="step4"> + <flow> + <step name="step1" next="step2"/> + <step name="step2"/> + </flow> + <flow> + <step name="step3"/> + </flow> + </split> + <step name="step4"/> +