当实现的构造函数具有要注入的依赖项时的工厂模式

Question

我正在处理私人事务，我遇到了一个需要其他意见的问题。我有以下代码，我想在其中创建一个工厂模式来创建 PaymentStrategy:

的新实例

PaymentStrategy 界面

public interface PaymentStrategy {

  Optional<Payment> pay(String payerAccountNumber,
                        String sellerAccountNumber,
                        ProductOrder[] productOrder
  );
}

EmployeePaymentStrategy具有两个依赖项的实现

public class EmployeePaymentStrategy implements PaymentStrategy {

  private final ProfileRemoteProvider profileRemoteProvider;
  private final PaymentValidator      paymentValidator;

  @Autowired
  public EmployeePaymentStrategy(ProfileRemoteProvider profileRemoteProvider,
                                 PaymentValidator paymentValidator) {
    this.profileRemoteProvider = profileRemoteProvider;
    this.paymentValidator = paymentValidator;
  }

  @Override
  public Optional<Payment> pay(String payerAccountNumber,
                               String sellerAccountNumber,
                               ProductOrder[] productOrder) {
    ...
  }
}

我想知道如何处理工厂中的依赖关系class。 EmployeePaymentStrategy class 是注入这两个依赖项的正确位置吗？ 工厂模式是解决问题的最佳方式吗

PaymentStrategyFactory 我有问题

public class PaymentStrategyFactory {

  private PaymentStrategyFactory() {
  }

  public static PaymentStrategy getPaymentStrategy(AccountType payerAccountType,
                                                   AccountType sellerAccountType) {
    if (sellerAccountType == AccountType.COMPANY) {
      switch (payerAccountType) {
        case EMPLOYEE:
          return new EmployeePaymentStrategy(...); //TODO 
        case BASIC_USER:
          return ...
        default:
          //this exception is throw when a payer account type is unknown
          throw new RuntimeException("exception type will be more specific");
      }
    }
    //This exception is throw when a seller account type is not a seller
    throw new RuntimeException("exception type will be more specific");
  }
}

Answer 1

PaymentStrategyFactory 更新和工作

public class PaymentStrategyFactory {

  private static ApplicationContext context;
  private ApplicationContext applicationContext;

  @Autowired
  private PaymentStrategyFactory(ApplicationContext applicationContext) {
    this.applicationContext = applicationContext;
  }

  @PostConstruct
  private void initializeApplicationContext() {
    PaymentStrategyFactory.context = applicationContext;
    this.applicationContext = null;
  }

  @Override
  public void setApplicationContext(ApplicationContext context) throws BeansException {
    PaymentStrategyFactory.context = context;
  }

  public static PaymentStrategy getPaymentStrategy(AccountType payerAccountType,
                                                   AccountType sellerAccountType) {
    if (sellerAccountType == AccountType.COMPANY) {
      switch (payerAccountType) {
        case EMPLOYEE:
          return context.getBean(EmployeePaymentStrategy.class);
          // return new EmployeePaymentStrategy();
        case BASIC_USER:
           ...
        }
     } 
     throw ...
   }
}

除了下面 Ilya 的评论，this post 帮助我在使用 Spring 进行 DI（依赖注入）时处理静态成员。现在一切对我来说都很好。