java - When SpringMVC integrates hibernate validator for parameter verification, why doesn't it throw an exception directly?-PHP Chinese Network Q&A

Hello everyone, I have a question

1. Environment

spring 4.3.7 hibernate-validator-5.4.1

2. The configuration is as follows

   classpath:messages/messages classpath:messages/ValidationMessages

3.bean and Controller

public class UserRequest { @NotBlank(message = "{login.valid.username.notnull}") private String username; @NotBlank(message = "{login.valid.password.notnull}") private String password; public String getUsername() { return username; } public void setUsername(String username) { this.username = username; } public String getPassword() { return password; } public void setPassword(String password) { this.password = password; } }

@RequestMapping(value = "/login", method = RequestMethod.POST) @ResponseBody public Object login(@Valid @RequestBody UserRequest ur, BindingResult result, HttpServletRequest request) { log.debug("login"); if(result.hasErrors()) { return result.getAllErrors().get(0); } …… }

Question:
Why must we use result.hasErrors() to display judgment in the code?
Isn’t it more reasonable to verify that the fields in UserRequest do not meet the definition and just throw an exception directly?

@PostMapping(UriView.REST_KNOWLEDGE_POINTS) @ResponseBody public Result createKnowledgePoint(@Valid KnowledgePoint knowledgePoint, BindingResult bindingResult) { // 如有参数错误，则返回错误信息给客户端 if (bindingResult.hasErrors()) { return Result.fail(CommonUtils.getBindingMessage(bindingResult)); } knowledgePoint.setKnowledgePointId(CommonUtils.uuid()); knowledgePoint.setName(knowledgePoint.getName().trim()); mapper.createKnowledgePoint(knowledgePoint); return Result.ok("", knowledgePoint); } /** * BindingResult 中的错误信息很多，对用户不够友好，使用 getBindingMessage() * 提取对用户阅读友好的定义验证规则 message。 * * @param result 验证的结果对象 * @return 验证规则 message */ public static String getBindingMessage(BindingResult result) { StringBuffer sb = new StringBuffer(); for (FieldError error : result.getFieldErrors()) { // sb.append(error.getField() + " : " + error.getDefaultMessage() + "\n"); sb.append(error.getDefaultMessage() + "\n"); } return sb.toString(); }

reply all (2)

Peter_Zhu2017-06-23 09:15:55 2 floor

For example, when a parameter exception occurs, what we return to the front end is the specific parameter name and description of the exception, not all the exception information given by Spring. If Spring automatically throws an exception, then it is difficult for you to control the returned information.