We're updating the issue view to help you get more done. 

Validation can sometimes proceed to the next group in sequence even after one of the constraints generated a violation

Description

According to specification on group sequences.

If at least one constraint fails in a sequenced group, none of the constraints of the following groups in the sequence get validated

HV can sometime proceed to validating constraints from the next group in the sequence when the current group extends any other groups. Example of such sequence:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 interface Group1 extends Group11, Group12 {} interface Group11 {} interface Group12 {} interface Group2 {} @GroupSequence({ Foo.class, Group1.class, Group2.class }) class Foo { @NotNull(groups = SequenceTest.Group11.class) private String str1; @NotNull(groups = SequenceTest.Group12.class) private String str2; @NotNull(groups = SequenceTest.Group2.class) private String str3; }

In this case if either one of `str1` `str2` is null `str3` should not be validated. But it sometimes can be!

Environment

None

Status

Assignee

Marko Bekhta

Reporter

Marko Bekhta

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

Backport?

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Affects versions

6.1.0.Alpha4
6.0.16.Final

Priority

Minor