Spring Boot自动配置无法识别泛型类问题排查

问题背景 #

在基于Spring Boot 3.1.5开发的开源项目自动配置类OccurrentMongoAutoConfiguration中，尝试实现CloudEventConverter的自动实例化逻辑：当容器中不存在CloudEventConverter Bean时，通过依赖CloudEventTypeMapper创建默认实例。但启动应用时出现CloudEventTypeMapper Bean找不到的错误，即使手动定义该Bean也无法完成注入。

问题原因 #

1. 方法级泛型导致类型无法推断：occurrentCloudEventConverter方法声明了方法级泛型<T>，Spring无法确定该T的具体类型，会尝试寻找未绑定泛型的CloudEventTypeMapper Bean；而实际存在的是CloudEventTypeMapper<?>或CloudEventTypeMapper<GameEvent>这类带通配符/具体类型的Bean，无法匹配。
2. 泛型通配符不兼容：默认Bean返回CloudEventTypeMapper<?>，但方法参数要求CloudEventTypeMapper<T>，受泛型类型擦除和匹配规则限制，Spring无法将通配符类型适配到未确定的T类型参数。

解决方法 #

方案1：统一使用通配符适配泛型 #

修改occurrentCloudEventConverter方法的参数类型与Builder泛型为通配符，让Spring能够匹配所有类型的CloudEventTypeMapper Bean：

@Bean
@ConditionalOnMissingBean(CloudEventConverter.class)
public CloudEventConverter<?> occurrentCloudEventConverter(Optional<ObjectMapper> objectMapper, OccurrentProperties occurrentProperties, CloudEventTypeMapper<?> cloudEventTypeMapper) {
    ObjectMapper mapper = objectMapper.orElseGet(ObjectMapper::new);
    return new JacksonCloudEventConverter.Builder<>(mapper, occurrentProperties.getCloudEventConverter().getCloudEventSource())
            .typeMapper(cloudEventTypeMapper)
            .build();
}

方案2：调整默认Bean的泛型声明 #

将默认occurrentTypeMapper的返回类型改为具体泛型，让Spring明确识别Bean的类型：

@Bean
@ConditionalOnMissingBean(CloudEventTypeMapper.class)
public CloudEventTypeMapper<Object> occurrentTypeMapper() {
    return ReflectionCloudEventTypeMapper.qualified();
}

同时保持occurrentCloudEventConverter方法的参数为CloudEventTypeMapper<T>，此时Spring可以将CloudEventTypeMapper<Object>适配到泛型参数T。

方案3：移除方法级泛型 #

如果业务逻辑不需要方法级泛型，直接移除<T>，统一使用通配符：

@Bean
@ConditionalOnMissingBean(CloudEventConverter.class)
public CloudEventConverter<?> occurrentCloudEventConverter(Optional<ObjectMapper> objectMapper, OccurrentProperties occurrentProperties, CloudEventTypeMapper<?> cloudEventTypeMapper) {
    ObjectMapper mapper = objectMapper.orElseGet(ObjectMapper::new);
    return new JacksonCloudEventConverter.Builder<>(mapper, occurrentProperties.getCloudEventConverter().getCloudEventSource())
            .typeMapper(cloudEventTypeMapper)
            .build();
}

验证效果 #

修改后，无论是自动配置的默认CloudEventTypeMapper，还是手动定义的CloudEventTypeMapper<GameEvent>，都能被正确注入到occurrentCloudEventConverter方法中，应用可正常启动。

内容的提问来源于stack exchange，提问作者Johan