-
Notifications
You must be signed in to change notification settings - Fork 2.4k
validate step listeners #3708
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
Open
Open
validate step listeners #3708
+223
−153
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@hosuaby
hosuaby
force-pushed
the
feature/checkListeners
branch
from
May 10, 2020 18:58
d7e5bf7
to
cb71ecf
Compare
Works also with XML config:
<?xml version="1.0" encoding="UTF-8"?> <beans:beans xmlns="http://www.springframework.org/schema/batch" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:beans="http://www.springframework.org/schema/beans" xsi:schemaLocation="http://www.springframework.org/schema/batch http://www.springframework.org/schema/batch/spring-batch.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <job id="someJob"> <step id="someStep"> <tasklet ref="someTasklet"/> <listeners> <listener ref="dummyJobExecutionListener" /> </listeners> </step> </job> </beans:beans>
@fmbenhassine
fmbenhassine
added
the
status: waiting-for-triage
Issues that we did not analyse yet
label
May 12, 2020
@hosuaby
hosuaby
force-pushed
the
feature/checkListeners
branch
from
May 13, 2020 08:32
cb71ecf
to
b645523
Compare
@fmbenhassine
fmbenhassine
changed the title
(削除) FEATURE: validate step listeners (削除ここまで)
(追記) validate step listeners (追記ここまで)
Nov 9, 2020
@fmbenhassine
fmbenhassine
added
pr-for: bug
and removed
pr-for: enhancement
status: waiting-for-triage
Issues that we did not analyse yet
labels
Nov 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The problem:
StepBuilderFactory
is very permissive concerning listeners.Method
AbstractTaskletStepBuilder#listener(Object listener)
accepts an Object as parameter, and this can lead to wrong step configurations as following:As you see
DummyJobExecutionListener
is a job listener! Not step listener. Code compiles and executes without a single warning. This mis-configuration can lead to long painful hours of debugging, before user will notice that he passed wrong listener.Solution: add runtime assert that will check that Object listener is a valid step execution listener. We can simply use method
StepListenerFactoryBean#isListener
.With this feature, the precedent code will throw an exception during application start-up: