Spring Boot中泛型多实现Bean的构造器自动装配问题求助

问题场景 #

项目中存在承载通用预处理逻辑的OrderOperation泛型类，依赖不同的OrderService实现类（IceCreamService、BurgerService、PizzaService），这些实现类均实现了泛型接口OrderService<T extends Order, U extends OrderDto>。在Spring自动装配OrderOperation时，因存在多个匹配的OrderService Bean，导致注入冲突。尝试设置@Scope("prototype")未解决问题，希望保留generic service -> target service的调用结构。

相关代码结构：

// 订单服务实现类
public class IceCreamService implements OrderService<IcecreamOrder, IcecreamOrderDto> { ... }
public class BurgerService implements OrderService<BurgerOrder, BurgerOrderDto> { ... }
public class PizzaService implements OrderService<PizzaOrder, PizzaOrderDto> { ... }

// 泛型预处理类
public class OrderOperation<T extends Order, U extends OrderDto> {
    private final OrderService<T, U> targetService;
    ...
}

解决方案 #

方案1：利用Spring泛型类型自动匹配（推荐） #

Spring支持根据泛型参数解析匹配对应的Bean，只需确保OrderOperation为原型作用域（每个控制器需要独立实例），并通过构造器注入OrderService：

1. 修改OrderOperation，添加Spring注解并设置原型作用域：

@Service
@Scope("prototype")
public class OrderOperation<T extends Order, U extends OrderDto> {
    private final OrderService<T, U> targetService;

    // 构造器注入，让Spring自动匹配对应泛型的OrderService
    public OrderOperation(OrderService<T, U> targetService) {
        this.targetService = targetService;
    }

    // 通用预处理方法
    public U processOrder(T order) {
        // 预处理逻辑
        return targetService.process(order);
    }
}

2. 在控制器中注入带具体泛型参数的OrderOperation：

@RestController
@RequestMapping("/icecream")
public class IceCreamController {
    private final OrderOperation<IcecreamOrder, IcecreamOrderDto> orderOperation;

    @Autowired
    public IceCreamController(OrderOperation<IcecreamOrder, IcecreamOrderDto> orderOperation) {
        this.orderOperation = orderOperation;
    }

    // 控制器业务方法
}

Spring会根据控制器中OrderOperation的泛型参数，自动找到对应的IceCreamService Bean完成注入，不会产生冲突。

方案2：手动配置Bean实例 #

通过@Configuration类为每种订单类型创建对应的OrderOperation实例，明确绑定对应的OrderService：

1. 创建配置类：

@Configuration
public class OrderBeanConfig {

    @Bean
    public OrderOperation<IcecreamOrder, IcecreamOrderDto> iceCreamOrderOperation(IceCreamService iceCreamService) {
        return new OrderOperation<>(iceCreamService);
    }

    @Bean
    public OrderOperation<BurgerOrder, BurgerOrderDto> burgerOrderOperation(BurgerService burgerService) {
        return new OrderOperation<>(burgerService);
    }

    @Bean
    public OrderOperation<PizzaOrder, PizzaOrderDto> pizzaOrderOperation(PizzaService pizzaService) {
        return new OrderOperation<>(pizzaService);
    }
}

2. 在控制器中注入对应的Bean：

@RestController
@RequestMapping("/burger")
public class BurgerController {
    private final OrderOperation<BurgerOrder, BurgerOrderDto> burgerOrderOperation;

    @Autowired
    public BurgerController(OrderOperation<BurgerOrder, BurgerOrderDto> burgerOrderOperation) {
        this.burgerOrderOperation = burgerOrderOperation;
    }
}

这种方式完全由开发者控制Bean的创建逻辑，避免Spring自动匹配的歧义。

方案3：使用@Qualifier限定符 #

为每个OrderService实现类添加唯一的限定符，注入时明确指定：

1. 给OrderService实现类添加@Qualifier：

@Service
@Qualifier("iceCreamService")
public class IceCreamService implements OrderService<IcecreamOrder, IcecreamOrderDto> { ... }

@Service
@Qualifier("burgerService")
public class BurgerService implements OrderService<BurgerOrder, BurgerOrderDto> { ... }

2. 修改OrderOperation的构造器，添加@Qualifier参数（或在注入时指定）：

@Service
@Scope("prototype")
public class OrderOperation<T extends Order, U extends OrderDto> {
    private final OrderService<T, U> targetService;

    public OrderOperation(@Qualifier("iceCreamService") OrderService<T, U> targetService) {
        this.targetService = targetService;
    }
}

注：此方式需为每种OrderOperation实例单独配置限定符，灵活性较低，适合订单类型较少的场景。

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