Spring Boot Flight与Seat服务循环依赖问题求解

针对你遇到的FlightService与SeatService循环依赖、@Lazy未生效且不想大幅改动架构的问题，以下几个简洁方案可以快速解决：

1. 构造器注入时精准使用@Lazy注解 #

如果当前用的是构造器注入，@Lazy需要标注在依赖的参数上，而非类上，这样Spring会为依赖创建代理对象，延迟初始化以打破循环。

示例代码：

// FlightServiceImp.java
@Service
public class FlightServiceImp implements FlightService {
    private final SeatService seatService;
    private final FlightRepository flightRepository;

    // 在SeatService参数上添加@Lazy
    public FlightServiceImp(@Lazy SeatService seatService, FlightRepository flightRepository) {
        this.seatService = seatService;
        this.flightRepository = flightRepository;
    }

    @Override
    public Flight addFlight(Flight flight) {
        flight = flightRepository.save(flight);
        seatService.createSeatsForFlight(flight);
        return flight;
    }
}

// SeatServiceImp.java
@Service
public class SeatServiceImp implements SeatService {
    private final FlightService flightService;
    private final SeatRepository seatRepository;

    // 这里如果FlightService的方法不会在SeatService初始化阶段调用，无需加@Lazy
    public SeatServiceImp(FlightService flightService, SeatRepository seatRepository) {
        this.flightService = flightService;
        this.seatRepository = seatRepository;
    }

    @Override
    public void createSeatsForFlight(Flight flight) {
        // 生成座位逻辑
        List<Seat> seats = generateSeats(flight);
        seatRepository.saveAll(seats);
    }
}

2. 改用Setter注入代替构造器注入 #

Spring对Setter注入的循环依赖支持更完善，将其中一个服务的依赖注入方式改为Setter，配合@Autowired即可自动处理循环。

示例代码：

// FlightServiceImp.java
@Service
public class FlightServiceImp implements FlightService {
    private SeatService seatService;
    private final FlightRepository flightRepository;

    // 构造器只注入Repository
    public FlightServiceImp(FlightRepository flightRepository) {
        this.flightRepository = flightRepository;
    }

    // Setter注入SeatService
    @Autowired
    public void setSeatService(SeatService seatService) {
        this.seatService = seatService;
    }

    @Override
    public Flight addFlight(Flight flight) {
        flight = flightRepository.save(flight);
        seatService.createSeatsForFlight(flight);
        return flight;
    }
}

SeatServiceImp保持原构造器注入即可，Spring会自动完成两个服务的初始化。

3. 调整DBSeeder的执行时机 #

如果循环依赖的触发点是DBSeeder初始化阶段调用FlightService，可将DBSeeder改为实现ApplicationRunner或CommandLineRunner接口，这样初始化逻辑会在Spring上下文完全加载完成后执行，避免在Bean初始化阶段触发循环依赖。

示例代码：

@Component
public class DBSeeder implements ApplicationRunner {
    private final FlightService flightService;

    public DBSeeder(FlightService flightService) {
        this.flightService = flightService;
    }

    @Override
    public void run(ApplicationArguments args) throws Exception {
        // 初始化航班的逻辑放在这里执行
        initTestFlights();
    }

    private void initTestFlights() {
        Flight testFlight = new Flight();
        // 设置航班属性（如航班号、起降时间等）
        flightService.addFlight(testFlight);
    }
}

4. 通过ApplicationContext延迟获取依赖 #

在其中一个服务中注入ApplicationContext，在需要使用另一个服务时再通过上下文获取，避免直接注入导致循环。

示例代码：

// FlightServiceImp.java
@Service
public class FlightServiceImp implements FlightService {
    private final ApplicationContext context;
    private final FlightRepository flightRepository;

    public FlightServiceImp(ApplicationContext context, FlightRepository flightRepository) {
        this.context = context;
        this.flightRepository = flightRepository;
    }

    @Override
    public Flight addFlight(Flight flight) {
        flight = flightRepository.save(flight);
        // 延迟获取SeatService
        SeatService seatService = context.getBean(SeatService.class);
        seatService.createSeatsForFlight(flight);
        return flight;
    }
}

这种方式无需修改SeatService的依赖关系，快速打破循环，但注意不要滥用，仅用于临时解耦场景。

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