<stop /> applies only to externalized flow, not to surrounding job

[arno]

using a <stop /> tag from within an externalized flow/job stops the flow/job execution, but not the surrounding job. So the flow/job stops, but the surrounding job keeps running, moving on to the step following the externalized flow/job.

This behavior makes sense, but is it the expected behavior? Wouldn't stopping the whole execution (i.e. surrounding job execution) make more sense?

[Dave Syer]

Thanks, Arnaud. I don't think that was intentional. Can you raise a JIRA?

[arno]

JIRA created: https://jira.springsource.org/browse/BATCH-1710