I have a spring batch application (version 5.1.2) and was migrating from the EnableBatchProcessing-Annotation to the programatic configuration by implementing DefaultBatchConfiguration-Class.

I did this in order to provide my own TaskExecutor so multiple batch-jobs can run in parallel and to provide my own PlatformTransactionManager.

My jobs datasource-config and datasource are defined in separate configuration classes.

When running the application I get the following warnings

Bean 'myDataSourceConfig' of type [dataImporter.config.sql.MyDataSourceConfig$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [jobRegistryBeanPostProcessor]?

Bean 'myDataSource' of type [com.zaxxer.hikari.HikariDataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying).

Bean 'batchJobConfiguration' of type [dataImporter.batchjobs.BatchJobConfiguration$$SpringCGLIB$$0] is not eligible for g...

Bean 'jobRegistry' of type [org.springframework.batch.core.configuration.support.MapJobRegistry] is not eligible for getting processed by all ...