Improve docs on controller method validation

Closes gh-32807

framework-docs/modules/ROOT/pages/web/webflux/controller/ann-validation.adoc

@@ -3,28 +3,40 @@
 
 [.small]#xref:web/webmvc/mvc-controller/ann-validation.adoc[See equivalent in the Servlet stack]#
 
-Spring WebFlux has built-in xref:core/validation/validator.adoc[Validation] support for
+Spring WebFlux has built-in xref:core/validation/validator.adoc[Validation] for
-`@RequestMapping` methods, including the option to use
+`@RequestMapping` methods, including xref:core/validation/beanvalidation.adoc[Java Bean Validation].
-xref:core/validation/beanvalidation.adoc[Java Bean Validation].
+Validation may be applied at one of two levels:
-The validation support works on two levels.
 
-First, resolvers for
+1. xref:web/webflux/controller/ann-methods/modelattrib-method-args.adoc[@ModelAttribute],
-xref:web/webflux/controller/ann-methods/modelattrib-method-args.adoc[@ModelAttribute],
 xref:web/webflux/controller/ann-methods/requestbody.adoc[@RequestBody], and
-xref:web/webflux/controller/ann-methods/multipart-forms.adoc[@RequestPart] method
+xref:web/webflux/controller/ann-methods/multipart-forms.adoc[@RequestPart] argument
-parameters perform validation if the parameter has Jakarta's `@Valid` or Spring's
+resolvers validate a method argument individually if the method parameter is annotated
-`@Validated` annotation, and raise `MethodArgumentNotValidException` if necessary.
+with Jakarta `@Valid` or Spring's `@Validated`, _AND_ there is no `Errors` or
-Alternatively, you can handle the errors in the controller method by adding an
+`BindingResult` parameter immediately after, _AND_ method validation is not needed (to be
-`Errors` or `BindingResult` method parameter immediately after the validated one.
+discussed next). The exception raised in this case is `MethodArgumentNotValidException`.
-
+
-Second, if {bean-validation-site}[Java Bean Validation] is present _AND_ any method
+2. When `@Constraint` annotations such as `@Min`, `@NotBlank` and others are declared
-parameter has `@Constraint` annotations, then method validation is applied instead,
+directly on method parameters, or on the method (for the return value), then method
-raising `HandlerMethodValidationException` if necessary. For this case you can still add
+validation must be applied, and that supersedes validation at the method argument level
-an `Errors` or `BindingResult` method parameter to handle validation errors within the
+because method validation covers both method parameter constraints and nested constraints
-controller method, but if other method arguments have validation errors then
+via `@Valid`. The exception raised in this case is `HandlerMethodValidationException`.
-`HandlerMethodValidationException` is raised instead. Method validation can apply
+
-to the return value if the method is annotated with `@Valid` or with `@Constraint`
+Applications must handle both `MethodArgumentNotValidException` and
-annotations.
+`HandlerMethodValidationException` as either may be raised depending on the controller
+method signature. The two exceptions, however are designed to be very similar, and can be
+handled with almost identical code. The main difference is that the former is for a single
+object while the latter is for a list of method parameters.
+
+NOTE: `@Valid` is not a constraint annotation, but rather for nested constraints within
+an Object. Therefore, by itself `@Valid` does not lead to method validation. `@NotNull`
+on the other hand is a constraint, and adding it to an `@Valid` parameter leads to method
+validation. For nullability specifically, you may also use the `required` flag of
+`@RequestBody` or `@ModelAttribute`.
+
+Method validation may be used in combination with `Errors` or `BindingResult` method
+parameters. However, the controller method is called only if all validation errors are on
+method parameters with an `Errors` immediately after. If there are validation errors on
+any other method parameter then `HandlerMethodValidationException` is raised.
 
 You can configure a `Validator` globally through the
 xref:web/webflux/config.adoc#webflux-config-validation[WebMvc config], or locally

framework-docs/modules/ROOT/pages/web/webmvc/mvc-controller/ann-validation.adoc

@@ -3,28 +3,40 @@
 
 [.small]#xref:web/webflux/controller/ann-validation.adoc[See equivalent in the Reactive stack]#
 
-Spring MVC has built-in xref:core/validation/validator.adoc[Validation] support for
+Spring MVC has built-in xref:core/validation/validator.adoc[validation] for
-`@RequestMapping` methods, including the option to use
+`@RequestMapping` methods, including xref:core/validation/beanvalidation.adoc[Java Bean Validation].
-xref:core/validation/beanvalidation.adoc[Java Bean Validation].
+Validation may be applied at one of two levels:
-The validation support works on two levels.
 
-First, resolvers for
+1. xref:web/webmvc/mvc-controller/ann-methods/modelattrib-method-args.adoc[@ModelAttribute],
-xref:web/webmvc/mvc-controller/ann-methods/modelattrib-method-args.adoc[@ModelAttribute],
 xref:web/webmvc/mvc-controller/ann-methods/requestbody.adoc[@RequestBody], and
-xref:web/webmvc/mvc-controller/ann-methods/multipart-forms.adoc[@RequestPart] method
+xref:web/webmvc/mvc-controller/ann-methods/multipart-forms.adoc[@RequestPart] argument
-parameters perform validation if the parameter has Jakarta's `@Valid` or Spring's
+resolvers validate a method argument individually if the method parameter is annotated
-`@Validated` annotation, and raise `MethodArgumentNotValidException` if necessary.
+with Jakarta `@Valid` or Spring's `@Validated`, _AND_ there is no `Errors` or
-Alternatively, you can handle the errors in the controller method by adding an
+`BindingResult` parameter immediately after, _AND_ method validation is not needed (to be
-`Errors` or `BindingResult` method parameter immediately after the validated one.
+discussed next). The exception raised in this case is `MethodArgumentNotValidException`.
-
+
-Second, if {bean-validation-site}[Java Bean Validation] is present _AND_ any method
+2. When `@Constraint` annotations such as `@Min`, `@NotBlank` and others are declared
-parameter has `@Constraint` annotations, then method validation is applied instead,
+directly on method parameters, or on the method (for the return value), then method
-raising `HandlerMethodValidationException` if necessary. For this case you can still add
+validation must be applied, and that supersedes validation at the method argument level
-an `Errors` or `BindingResult` method parameter to handle validation errors within the
+because method validation covers both method parameter constraints and nested constraints
-controller method, but if other method arguments have validation errors then
+via `@Valid`. The exception raised in this case is `HandlerMethodValidationException`.
-`HandlerMethodValidationException` is raised instead. Method validation can apply
+
-to the return value if the method is annotated with `@Valid` or with `@Constraint`
+Applications must handle both `MethodArgumentNotValidException` and
-annotations.
+`HandlerMethodValidationException` as either may be raised depending on the controller
+method signature. The two exceptions, however are designed to be very similar, and can be
+handled with almost identical code. The main difference is that the former is for a single
+object while the latter is for a list of method parameters.
+
+NOTE: `@Valid` is not a constraint annotation, but rather for nested constraints within
+an Object. Therefore, by itself `@Valid` does not lead to method validation. `@NotNull`
+on the other hand is a constraint, and adding it to an `@Valid` parameter leads to method
+validation. For nullability specifically, you may also use the `required` flag of
+`@RequestBody` or `@ModelAttribute`.
+
+Method validation may be used in combination with `Errors` or `BindingResult` method
+parameters. However, the controller method is called only if all validation errors are on
+method parameters with an `Errors` immediately after. If there are validation errors on
+any other method parameter then `HandlerMethodValidationException` is raised.
 
 You can configure a `Validator` globally through the
 xref:web/webmvc/mvc-config/validation.adoc[WebMvc config], or locally through an