NumberFormatException caused by property paths from JSR-303 based validation with no index into a collection [SPR-16177]

[spring-projects-issues]

Ricardo Malikoski opened SPR-16177 and commented

When a I have a custom validator to child collection that can't be indexed, (example attached with Set.class), fails. The problem is the same with #13276.

---

Affects: 4.3.12, 5.0.1

Reference URL: #13276

Attachments:

• spring-validator-test.zip (11.95 kB)

Issue Links:

• SpringValidatorAdapter is incorrectly resolving rejected value for bean based field level constraints [SPR-9332] #13970 SpringValidatorAdapter is incorrectly resolving rejected value for bean based field level constraints
• GenericConversionService.convert() throws IllegalArgumentException after updating to Spring 3.2.1 [SPR-10243] #14876 GenericConversionService.convert() throws IllegalArgumentException after updating to Spring 3.2.1
• NumberFormatException caused by property paths from JSR-303 based validation with no index into a collection [SPR-8634] #13276 NumberFormatException caused by property paths from JSR-303 based validation with no index into a collection
• Spring validation crashes with Hibernate Validation 5 style list constraint violations [SPR-15082] #19648 Spring validation crashes with Hibernate Validation 5 style list constraint violations

Referenced from: commits 9779b8b, 3091fee

Backported to: 4.3.13

[spring-projects-issues]

Juergen Hoeller commented

Good catch! I've revised the condition in SpringValidatorAdapter.getRejectedValue to always skip field paths with a "[]" inside (rather than just behind the invalidValue==leafBean condition).

This will be available in the upcoming 5.0.2.BUILD-SNAPSHOT, and backported to 4.3.13 later today.

[spring-projects-issues]

Ricardo Malikoski commented

Thanks Juergen.