How to solve the pits encountered with @ Validated and BindingResult

This article mainly introduces "how to solve the pits encountered in the use of @ Validated and BindingResult". In the daily operation, I believe many people have doubts about how to solve the pits encountered in the use of @ Validated and BindingResult. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts about "how to solve the pits encountered in the use of @ Validated and BindingResult"! Next, please follow the editor to study!

@ Validated and BindingResult use the pit encountered

@ Validated and BindingResult need to be adjacent, otherwise the variable result cannot accept error messages

Console output

Field error in object 'entity' on field' variable: rejected value [null]; codes [NotNull.entity. Variable, NotNull. Variable, NotNull.java.lang.String,NotNull]; arguments [org.springframework.context.support.DefaultMessageSourceResolvable: codes

Screenshot of the correct content

@ Validated @ Valid three kinds of exception catch handling

There are three kinds of anomalies

BindException: form submission is valid and will be invalid for submission in json format

MethodArgumentNotValidException: the preceding paragraph is valid in json format

ConstraintViolationException: add @ RequestParam to the parameter or @ NotBlank @ NotNull to the parameter

At this point, the study on "how to solve the pit encountered in the use of @ Validated and BindingResult" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!