NestedPath is ignored when validating nested Entities [DATAREST-718]

Tim Meißner opened DATAREST-718 and commented

I have a rest resource "dashboard" which has a list of embedded resources (no repository for them) of class "widget". I have a class DashboardValidator and a WidgetValidator. Now i want to validate the dashboard resource before saving it, by validating each object of class widget with the widget validator.

for (int i = 0; i < dashboard.getWidgets().size(); i++) {
           Widget widget = dashboard.getWidgets().get(i);
           errors.pushNestedPath("widgets["+i+"]");
           ValidationUtils.invokeValidator(widgetValidator, widget, errors);
           errors.popNestedPath();
       }

The response i get is the following:

errors: [{entity: "Dashboard", message: "Widget name should not be empty", invalidValue: "Test",…}]}
errors: [{entity: "Dashboard", message: "Widget name should not be empty", invalidValue: "Test",…}]
0: {entity: "Dashboard", message: "Widget name should not be empty", invalidValue: "Test",…}
entity: "Dashboard"
invalidValue: "Test"
message: "Widget name should not be empty"
property: "name"

I posted a Dashboard called "Test" with a widget that has an empty name. Obviously the error doesn't indicate that widget[0].name is the rejected property and the invalidValue property is also wrong (because it shows the dashboards name and not the name of the embedded widget which caused the error)

Affects: 2.4.1 (Gosling SR1)