Spring MVC @Valid annotation for all controllers?

Question

Iv'e seen this nice mechanism:

http://www.mkyong.com/spring-mvc/spring-3-mvc-and-jsr303-valid-example/

Is it possible to make the @Valid annotation avaialble for all the Controllers with validation? It seems very redundant to do the following:

@RequestMapping(value = "/getPlayerAccounts", method = RequestMethod.POST, consumes = MediaType.APPLICATION_JSON_VALUE)
@ResponseStatus(value = HttpStatus.OK)
@ResponseBody
public QueryResultsDTO<PlayerAccountResultDTO> getPlayerAccounts(@RequestBody **@Valid** FilteredQueryRequestDTO filteredQueryRequestDTO,
                                 **BindingResult result**) {

**this.validateDTO(result);**
return this.playerService.getPlayerAccounts(filteredQueryRequestDTO);
}

Reduandant code:

@Valid

BindingResult result

this.validateDTO(result);

These seems like a recurring pattern, probably someone already solved it? maybe with aspects? I dont care that all my methods and controllers will have the @Valid login, most of the DTOs they recieve will be valid anyway (since no validation annotations are applied to them)

Thanks

You sure can do it with aspects. But I am not sure wether this is really worth the hassle. — Markus W Mahlberg, Nov 18 '14 at 14:59
So you think validating in each controller is a better solution? Thinking about a developer that forgets to add @Valid annotation make me feel dizzy — Urbanleg, Nov 18 '14 at 15:22
I don't see it as an issue. Each layer of abstraction adds complexity, complexity tends to come with bugs and problems. — Markus W Mahlberg, Nov 18 '14 at 16:06
It would cost you more time dealing with how to get rid of the "redundant code" then just typing a the few words that you consider redundant. ps: if you consider that piece of code redundant half of the Java syntax could be considered redundant. — Jonas Geiregat, Nov 18 '14 at 22:36

score 3 · Answer 1 · answered Nov 19 '14 at 09:48

you cannot omit @Valid annotation, since this is the way to tell spring which dto to validate, that is just the way the spring validation works. But having a BindingResult result to each of your methods is not necessary. You may omit it completely. If you want to do something when validation fails, you can catch the MethodArgumentNotValidException that is thrown in that case from an exception handling method (e.g you can use a class with @ControllerAdvice annotations that will contain @ExceptionHandler methods applied to all controllers - exception handling is a whole different topic, you can read more details on related spring mvc exception handling documentation)

Don't know if things changed since '14 but I could ommit @Valid and enforce validation always. This is the way could make it: https://stackoverflow.com/questions/44722000/how-to-spring-get-rid-of-validate-for-automatic-controller-validation — Gerard Bosch, Aug 05 '17 at 14:12

Spring MVC @Valid annotation for all controllers?

1 Answers1

Linked