Simplify GroupSequence for ordered checking

Description

The JSR 303 is becoming defacto solution at enterprise level projects however I think that it has a significant useless part. The current implementation states group sequence must be utilized to ordered validation. In order to use group sequence, one has to define interfaces for each order sequence such this:

Look the code how it is ugly and useless. What I am offering is a simplified version of ordering such this:

Almost all enterprise projects needs such kind of things. For example lets say that you want to validate email field by NotEmpty and UniqueAtDatabase. Why should we show two error messages in this case? Shortly, to increase usability and adaptability please solve this issue.

PS: This issue is cross posted here and forums.

https://forum.hibernate.org/viewtopic.php?f=26&t=1007328

Environment

None

Assignee

Unassigned

Reporter

Cemo Koc

Labels

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Affects versions

Priority

Major
Configure