Skip to content

Make JobOperator extend JobLauncher #4832

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.

Sign up for GitHub

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

Jump to bottom
Closed
fmbenhassine opened this issue May 7, 2025 · 0 comments
Closed

Make JobOperator extend JobLauncher #4832

fmbenhassine opened this issue May 7, 2025 · 0 comments
Labels
in: core type: enhancement
Milestone
6.0.0-M1

Comments

@fmbenhassine
Copy link
Contributor

JobOperator is nothing more than a JobLauncher with more capabilities (it's start method uses JobLauncher#run behind the scenes). Therefore, it should technically be an extension of JobLauncher, adding stop/restart functionality on top of just running jobs.

This issue is to make JobOperator extend JobLauncher, which will greatly simplify the default batch configuration by removing the requirement to define two beans instead of one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
in: core type: enhancement
Projects
None yet
Milestone
6.0.0-M1
Development

No branches or pull requests
1 participant
@fmbenhassine