有这样一个场景:
订单服务与用户服务的循环依赖
假设在一个电商系统中,我们有两个服务类:OrderService 和 UserService。
OrderService 需要访问用户服务来获取或更新订单关联的用户信息。例如,当处理订单时,可能需要检查用户的信用状态或地址信息。
@Service
public class OrderService {
@Autowired
private UserService userService;
public void processOrder(Order order) {
User user = userService.getUserById(order.getUserId());
// ...进一步的业务逻辑
}
}
UserService 同样也需要访问订单服务,比如为了统计用户的购买行为或者计算用户的积分,这可能涉及到查询某个用户下的所有订单。
@Service
public class UserService {
@Autowired
private OrderService orderService;
public User getUserWithOrders(int userId) {
User user = getUserById(userId);
List<Order> orders = orderService.getOrdersByUserId(userId);
user.setOrders(orders);
return user;
}
}
在这个案例中,OrderService 类中注入了 UserService,而 UserService 类中又注入了 OrderService。这就构成了一个循环依赖:OrderService → UserService → OrderService。
启动时会报错类似这样:
Description:
The dependencies of some of the beans in the application context form a cycle:
xxxxxxx
解决
使用@Layz懒加载策略解决;
调整后的代码:
@Service
public class OrderService {
@Autowired
private UserService userService;
public void processOrder(Order order) {
User user = userService.getUserById(order.getUserId());
// ...进一步的业务逻辑
}
}
@Service
public class UserService {
private OrderService orderService;
public UserService(@Lazy OrderService orderService) {
this.orderService= orderService;
}
public User getUserWithOrders(int userId) {
User user = getUserById(userId);
List<Order> orders = orderService.getOrdersByUserId(userId);
user.setOrders(orders);
return user;
}
}