如何手动调用Spring Validator的validate()方法及复用PATCH请求验证

我希望手动调用实现了org.springframework.validation.Validator接口的验证器中的validate(Object target, Errors errors)方法。在控制器类中通过@InitBinder绑定该验证器时，Spring会自动传入Errors对象，但手动调用时我不知道该从何处获取该对象。虽然创建新的BeanPropertyBindingResult可以完成调用，但无法得到原本那种描述性的错误响应体。

请问是否可以从某处获取BeanPropertyBindingResult对象来执行手动验证？或者有没有更优的方式验证PATCH请求？这类请求较为特殊，需要先获取待更新的对象，之后执行验证才有意义，并且我希望复用POST请求的验证逻辑。

相关代码 #

控制器类 #

@Controller
public class MyController {

  private final MyValidator myValidator;
  private final MyService myService;

  @InitBinder("postRequest")
  public void initBinder(WebDataBinder binder) {
    binder.addValidators(myValidator);
  }

  // 控制器通过@InitBinder绑定的验证正常工作
  @PostMapping
  public void postWithBoundValidation(@RequestBody PostRequest request) {
    myService.doSomething(request);
  }

  // 需要在服务中执行相同的验证逻辑
  @PatchMapping
  public void postWithManualValidation(@RequestBody PatchRequest request) {
    myService.doSomethingWithManualValidation(request);
  }
}

服务类 #

@Service
public class MyService {
  
  private final MyValidator myValidator;
  private final MyRepo myRepo;

  public void doSomething(PostRequest postRequest) {
    // 业务逻辑
  }

  public void doSomethingWithManualValidation(PatchRequest patchRequest) {
    MyEntity entity = myRepo.findMyEntity();
    PostRequest postRequest = PostRequest.from(patchRequest, entity);
    
    // 如何正确构造这个Errors对象？
    Errors errors = new BeanPropertyBindingResult(postRequest, "patchRequest");

    // 此时才应该执行验证
    myValidator.validate(postRequest, errors);

    // 后续业务逻辑
  }
}

验证器类 #

@Component
public class MyValidator implements org.springframework.validation.Validator {
  @Override
  public boolean supports(Class<?> clazz) {
    return PostRequest.class.isAssignableFrom(clazz);
  }

  @Override
  public void validate(Object target, Errors errors) {
    // 具体验证逻辑示例
    PostRequest request = (PostRequest) target;
    if (request.getName() == null || request.getName().isEmpty()) {
      errors.rejectValue("name", "field.required", "名称不能为空");
    }
  }
}

1. 复用WebDataBinder生成标准Errors对象（推荐） #

通过注入WebDataBinderFactory，可以创建和控制器中逻辑完全一致的BindingResult，验证后抛出Spring标准异常MethodArgumentNotValidException，让框架自动生成和POST请求相同的描述性错误响应体。

修改服务类代码如下：

@Service
public class MyService {
  
  private final MyValidator myValidator;
  private final MyRepo myRepo;
  private final WebDataBinderFactory binderFactory;

  // 构造方法注入WebDataBinderFactory
  public MyService(MyValidator myValidator, MyRepo myRepo, WebDataBinderFactory binderFactory) {
    this.myValidator = myValidator;
    this.myRepo = myRepo;
    this.binderFactory = binderFactory;
  }

  public void doSomethingWithManualValidation(PatchRequest patchRequest) throws MethodArgumentNotValidException {
    MyEntity entity = myRepo.findMyEntity();
    PostRequest postRequest = PostRequest.from(patchRequest, entity);
    
    // 创建与控制器@InitBinder逻辑一致的WebDataBinder
    WebDataBinder binder = binderFactory.createBinder(null, postRequest, "postRequest");
    binder.addValidators(myValidator);
    // 执行验证
    binder.validate();
    
    BindingResult errors = binder.getBindingResult();
    if (errors.hasErrors()) {
      // 抛出Spring标准验证异常，框架自动处理为标准错误响应
      throw new MethodArgumentNotValidException(null, errors);
    }

    // 执行后续业务逻辑
  }
}

优势：完全复用Spring的验证机制，错误响应格式和POST请求完全一致，无需额外编写错误响应的处理逻辑。

2. 手动构造BindingResult并适配错误响应 #

如果无法注入WebDataBinderFactory，可以手动创建BeanPropertyBindingResult，然后收集错误信息并封装成标准格式，或通过自定义异常+全局异常处理器实现统一响应。

服务类修改 #

public void doSomethingWithManualValidation(PatchRequest patchRequest) {
  MyEntity entity = myRepo.findMyEntity();
  PostRequest postRequest = PostRequest.from(patchRequest, entity);
  
  Errors errors = new BeanPropertyBindingResult(postRequest, "postRequest");
  myValidator.validate(postRequest, errors);
  
  if (errors.hasErrors()) {
    // 抛出自定义异常，携带错误信息
    throw new ValidationFailedException(errors.getFieldErrors());
  }
  
  // 业务逻辑
}

全局异常处理器 #

@ControllerAdvice
public class GlobalValidationExceptionHandler {

  @ExceptionHandler(ValidationFailedException.class)
  public ResponseEntity<Map<String, Object>> handleValidationFailed(ValidationFailedException ex) {
    Map<String, Object> response = new HashMap<>();
    response.put("timestamp", LocalDateTime.now());
    response.put("status", HttpStatus.BAD_REQUEST.value());
    
    // 封装与Spring默认一致的字段错误信息
    List<Map<String, String>> errorDetails = ex.getFieldErrors().stream()
        .map(fieldError -> {
          Map<String, String> detail = new HashMap<>();
          detail.put("field", fieldError.getField());
          detail.put("message", fieldError.getDefaultMessage());
          detail.put("rejectedValue", String.valueOf(fieldError.getRejectedValue()));
          return detail;
        })
        .collect(Collectors.toList());
    
    response.put("errors", errorDetails);
    
    return new ResponseEntity<>(response, HttpStatus.BAD_REQUEST);
  }

  // 自定义异常类
  static class ValidationFailedException extends RuntimeException {
    private final List<FieldError> fieldErrors;

    public ValidationFailedException(List<FieldError> fieldErrors) {
      this.fieldErrors = fieldErrors;
    }

    public List<FieldError> getFieldErrors() {
      return fieldErrors;
    }
  }
}

3. PATCH请求验证的优化建议 #

• 验证逻辑单一职责：确保MyValidator只负责验证PostRequest的业务规则，不管是POST还是PATCH场景都直接复用该验证器，避免重复代码。
• 避免在服务层处理响应：优先使用方案1，通过抛出标准异常让框架处理响应，保持服务层专注于业务逻辑，不耦合HTTP响应细节。

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