You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that getFieldType will be called already with a fixedField parameter. However, getFieldType again invokes fixedField(String) with the passed string. So in the end the fixedField method will be called twice, which in turn prepends a nestedPath twice.
The quickfix is most probably to change the second line of resolveMessageCodes into
Class fieldType = getFieldType(field);
Oliver Becker opened SPR-7019 and commented
When validating nested properties, Spring computes a wrong property path (a.k.a. fieldname).
See org.springframework.validation.AbstractBindingResult
The problem is that getFieldType will be called already with a fixedField parameter. However, getFieldType again invokes fixedField(String) with the passed string. So in the end the fixedField method will be called twice, which in turn prepends a nestedPath twice.
The quickfix is most probably to change the second line of resolveMessageCodes into
Class fieldType = getFieldType(field);
Affects: 3.0.1
Referenced from: commits a2c3274
The text was updated successfully, but these errors were encountered: