java - SpringMVC集成hibernate validator進(jìn)行參數(shù)驗(yàn)證時(shí),為什么不直接拋異常?
問(wèn)題描述
各位大神好,請(qǐng)教個(gè)問(wèn)題
1.環(huán)境
spring 4.3.7hibernate-validator-5.4.1
2.配置如下
<bean name='messageSource'><property name='basenames'> <list><value>classpath:messages/messages</value><value>classpath:messages/ValidationMessages</value> </list></property><property name='useCodeAsDefaultMessage' value='false' /><property name='defaultEncoding' value='UTF-8' /><property name='cacheSeconds' value='60' /> </bean> <bean class='org.springframework.validation.beanvalidation.LocalValidatorFactoryBean'><property name='providerClass' value='org.hibernate.validator.HibernateValidator'/><property name='validationMessageSource' ref='messageSource'/> </bean> <mvc:annotation-driven validator='validator' />
3.bean和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); } …… }
問(wèn)題:為什么一定要在代碼中用result.hasErrors()顯示判斷?難道不能驗(yàn)證UserRequest中的字段不符合定義就直接拋異常,這樣不更合理些嗎?
問(wèn)題解答
回答1:問(wèn)題:為什么一定要在代碼中用result.hasErrors()顯示判斷?難道不能驗(yàn)證UserRequest中的字段不符合定義就直接拋異常,這樣不更合理些嗎?
例如我們?cè)趨?shù)異常的時(shí)候返回給前端的是異常的具體參數(shù)名和描述,不是 Spring 給出的所有異常信息,如果 Spring 自動(dòng)拋出異常,那么返回的信息你自己就不好控制了。
@PostMapping(UriView.REST_KNOWLEDGE_POINTS)@ResponseBodypublic Result createKnowledgePoint(@Valid KnowledgePoint knowledgePoint, BindingResult bindingResult) { // 如有參數(shù)錯(cuò)誤,則返回錯(cuò)誤信息給客戶端 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 中的錯(cuò)誤信息很多,對(duì)用戶不夠友好,使用 getBindingMessage() * 提取對(duì)用戶閱讀友好的定義驗(yàn)證規(guī)則 message。 * * @param result 驗(yàn)證的結(jié)果對(duì)象 * @return 驗(yàn)證規(guī)則 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();}回答2:
你只是在你的應(yīng)用場(chǎng)景中考慮為什么,一個(gè)框架更多的是考慮大多數(shù)時(shí)候怎么做最合理。
大部分對(duì)于客戶端數(shù)據(jù)的驗(yàn)證都不應(yīng)當(dāng)被當(dāng)作“異?!?,而是用戶在不知道的情況下被允許犯的錯(cuò)誤。
