Support user-defined ExecutionContextSerializer in BatchAutoConfiguation #38631
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.
Since Spring Batch 5, it's possible to easily specify a custom ExecutionContextSerializer by
@EnableBatchProcessing
as shown below:(The example is from https://spring.io/blog/2022/11/24/spring-batch-5-0-goes-ga )
However, when using BatchAutoConfiguration in Spring Boot, there isn’t a straightforward way to achieve this.
This pull request modifies the BatchAutoConfiguration to refer to an ExecutionContextSerializer registered in the ApplicationContext.
The behavior of the ExecutionContextSerializer has changed in Spring Batch 5.0. ( spring-projects/spring-batch#4122 )
So, if this feature is available, I expect it to be more helpful for those who prefer the behavior of old versions to upgrade to the latest version.
I believe the changes in this PR represent a user-expected behavior.
In Spring Batch, DefaultJobParametersConverter is used as a similar policy.
The class is used by default, but if there is another implementation class that the user has registered in ApplicationContext, it is replaced. And this is also a natural convention in Spring Boot.