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:
StepBuilderFactoryis 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
DummyJobExecutionListeneris 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: