You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add terminateOnly flag to RepeatContext. When a job is stopped it is different from a business operation voting to mark it as complete - the terminate flag probably should also set the complete flag, but clients (StepExecutor, JobExecutor) will do different things with the result. Also implies a new value in the BatchStatus enum (INTERRUPTED as distinct from STOPPED, FAILED).
Affects: 1.0-m2
Issue Links:
BATCH-40 An application developer must be able to control the 'exit codes' returned by the container
("is depended on by")
The text was updated successfully, but these errors were encountered:
Added additional flag to RepeatContext and test for it in StepInterruptionPolicy. Decided against the additional BatchStatus - a job which is complete because it is complete (even if set by the developer) is still COMPLETE. STOPPED is used to signal manual termination.
Dave Syer opened BATCH-48 and commented
Add terminateOnly flag to RepeatContext. When a job is stopped it is different from a business operation voting to mark it as complete - the terminate flag probably should also set the complete flag, but clients (StepExecutor, JobExecutor) will do different things with the result. Also implies a new value in the BatchStatus enum (INTERRUPTED as distinct from STOPPED, FAILED).
Affects: 1.0-m2
Issue Links:
("is depended on by")
The text was updated successfully, but these errors were encountered: