Using @Valid on a container (java.util.List) is deprecated

[verbitan]

Summary

Fixes deprecation warnings from Hibernate Validator about applying @Valid directly to container types.

Detail

Spring Boot 4.1.0 upgraded to Hibernate Validator 9.1 which included a change deprecating the use of @Valid at the container level.

Meaning that this:

class MyBean {
    @Valid
    List<MyContainerElement> list;
}

Should be replaced by this:

class MyBean {
    List<@Valid MyContainerElement> list;
}

Else these warnings are raised:

o.h.v.i.m.a.CascadingMetaDataBuilder     : HV000271: Using `@Valid` on a container (java.util.List) is deprecated. You should apply the annotation on the type argument(s). Affected element: routes
o.h.v.i.m.a.CascadingMetaDataBuilder     : HV000271: Using `@Valid` on a container (java.util.List) is deprecated. You should apply the annotation on the type argument(s). Affected element: predicates
o.h.v.i.m.a.CascadingMetaDataBuilder     : HV000271: Using `@Valid` on a container (java.util.List) is deprecated. You should apply the annotation on the type argument(s). Affected element: filters

[HDPark95]

One container-level @Valid in this change set looks like it was missed: GatewayMvcProperties.routesMap. It sits two fields below the routes you fixed in the same file and still triggers the same HV000271 — the deprecation applies to any container, Map included:

@NotNull
@Valid
private LinkedHashMap<String, RouteProperties> routesMap = new LinkedHashMap<>();

It's a live cascade target (bound as spring.cloud.gateway.server.webmvc.routes-map, iterated in RouterFunctionHolderFactory), so its RouteProperties values are validated. For a map the element annotation goes on the value type argument, mirroring the routes edit above:

@NotNull
private LinkedHashMap<String, @Valid RouteProperties> routesMap = new LinkedHashMap<>();

@NotNull stays on the field (it constrains the map reference, not the cascade). The three warnings quoted in the description are the webflux fields; the webmvc side logs the same for routesMap once those properties are bound and validated.

[verbitan]

One container-level @Valid in this change set looks like it was missed: GatewayMvcProperties.routesMap. It sits two fields below the routes you fixed in the same file and still triggers the same HV000271 — the deprecation applies to any container, Map included:

@NotNull
@Valid
private LinkedHashMap<String, RouteProperties> routesMap = new LinkedHashMap<>();

It's a live cascade target (bound as spring.cloud.gateway.server.webmvc.routes-map, iterated in RouterFunctionHolderFactory), so its RouteProperties values are validated. For a map the element annotation goes on the value type argument, mirroring the routes edit above:

@NotNull
private LinkedHashMap<String, @Valid RouteProperties> routesMap = new LinkedHashMap<>();

@NotNull stays on the field (it constrains the map reference, not the cascade). The three warnings quoted in the description are the webflux fields; the webmvc side logs the same for routesMap once those properties are bound and validated.

Good spot, thanks.