Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add terminateOnly flag to RepeatContext [BATCH-48] #3528

Closed
spring-projects-issues opened this issue Jul 15, 2007 · 2 comments
Closed

Add terminateOnly flag to RepeatContext [BATCH-48] #3528

spring-projects-issues opened this issue Jul 15, 2007 · 2 comments

Comments

@spring-projects-issues
Copy link
Collaborator

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:

  • BATCH-40 An application developer must be able to control the 'exit codes' returned by the container
    ("is depended on by")
@spring-projects-issues
Copy link
Collaborator Author

Dave Syer commented

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.

@spring-projects-issues
Copy link
Collaborator Author

Dave Syer commented

Assume closed as resolved and released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant