Spring Boot中Spring Batch模块化ApplicationContext配置：任务无法启动

在Spring Boot应用中配置两个Spring Batch任务时，为避免Bean名称冲突，采用ApplicationContextFactory创建独立上下文，开启@EnableBatchProcessing(modular=true)，并通过自定义@IgnoreDuringScan注解排除子配置类的组件扫描，但配置后任务无法启动。相关代码如下：

现有配置代码 #

模块化Job配置类 #

@Configuration
@EnableBatchProcessing(modular=true)
public class ModularJobConfig {

    @Bean
    public ApplicationContextFactory one() {
        return new GenericApplicationContextFactory(JobConfig1.class);
    }
 
    @Bean
    public ApplicationContextFactory two() {
        return new GenericApplicationContextFactory(JobConfig2.class);
    }
    
}

自定义排除扫描注解 #

@Target(ElementType.TYPE)
@Retention(RetentionPolicy.RUNTIME)
public @interface IgnoreDuringScan {
    
}

子Job配置类 #

@Configuration
@IgnoreDuringScan
public class JobConfig1 { ... }

@Configuration
@IgnoreDuringScan
public class JobConfig2 { ... }

主启动类 #

@SpringBootApplication
@ComponentScan(excludeFilters = @Filter(IgnoreDuringScan.class))
public class MainApplication { ...}

核心问题排查与解决 #

1. 子上下文未继承父上下文依赖 #

GenericApplicationContextFactory创建的子上下文默认不会继承父上下文的Bean（比如数据源、事务管理器、JobBuilderFactory等核心组件），如果子Job配置类中依赖这些Bean，会导致启动失败。

解决方法：改用AnnotationConfigApplicationContextFactory，并手动设置父上下文，让子上下文可以继承父上下文的必要Bean：

@Configuration
@EnableBatchProcessing(modular=true)
public class ModularJobConfig {

    private final ApplicationContext parentContext;

    // 注入父上下文
    public ModularJobConfig(ApplicationContext parentContext) {
        this.parentContext = parentContext;
    }

    @Bean
    public ApplicationContextFactory one() {
        AnnotationConfigApplicationContextFactory factory = new AnnotationConfigApplicationContextFactory(JobConfig1.class);
        factory.setParent(parentContext);
        return factory;
    }
 
    @Bean
    public ApplicationContextFactory two() {
        AnnotationConfigApplicationContextFactory factory = new AnnotationConfigApplicationContextFactory(JobConfig2.class);
        factory.setParent(parentContext);
        return factory;
    }
    
}

2. 组件扫描排除规则不明确 #

确保@ComponentScan的过滤规则明确指定注解类型，避免父上下文重复加载子Job配置类：

@SpringBootApplication
@ComponentScan(excludeFilters = @Filter(type = FilterType.ANNOTATION, classes = IgnoreDuringScan.class))
public class MainApplication {
    public static void main(String[] args) {
        SpringApplication.run(MainApplication.class, args);
    }
}

3. 子Job配置类完整性检查 #

确认每个子配置类中正确配置了Job、Step等Bean，且依赖的核心组件（如JobBuilderFactory、StepBuilderFactory）能正常从父上下文注入：

@Configuration
@IgnoreDuringScan
public class JobConfig1 {

    @Autowired
    private JobBuilderFactory jobBuilderFactory;

    @Autowired
    private StepBuilderFactory stepBuilderFactory;

    @Bean
    public Step sampleStep() {
        return stepBuilderFactory.get("sampleStep")
                .tasklet((contribution, chunkContext) -> {
                    // 自定义任务逻辑
                    return RepeatStatus.FINISHED;
                })
                .build();
    }

    @Bean
    public Job sampleJob() {
        return jobBuilderFactory.get("sampleJob")
                .start(sampleStep())
                .build();
    }
}

4. 日志排查Bean加载情况 #

启动应用时开启org.springframework包的DEBUG日志，查看父上下文和子上下文的Bean加载情况，确认子配置类仅在子上下文中被加载，且核心依赖Bean存在。

内容的提问来源于stack exchange，提问作者Sxc-Dev