You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of v4.3, @EnableBatchProcessing auto-configures a JobRegistry in the application context. So as a user, I still need to create a JobRegistryBeanPostProcessor bean myself to populate the registry:
@Bean
public JobRegistryBeanPostProcessor jobRegistryBeanPostProcessor(JobRegistry jobRegistry) {
JobRegistryBeanPostProcessor postProcessor = new JobRegistryBeanPostProcessor();
postProcessor.setJobRegistry(jobRegistry);
return postProcessor;
}
Since the JobRegistry is already created by @EnableBatchProcessing, this bean post processor could also be created by the annotation with the registry already set on it.
This also should apply to the programmatic way of configuration through DefaultBatchConfiguration introduced in v5.
As of v4.3,
@EnableBatchProcessing
auto-configures aJobRegistry
in the application context. So as a user, I still need to create aJobRegistryBeanPostProcessor
bean myself to populate the registry:Since the
JobRegistry
is already created by@EnableBatchProcessing
, this bean post processor could also be created by the annotation with the registry already set on it.This also should apply to the programmatic way of configuration through
DefaultBatchConfiguration
introduced in v5.References:
The text was updated successfully, but these errors were encountered: