<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 5 janv. 2012, at 21:53, Cemo wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; "><div style="word-wrap: break-word; "><div><div><div><br class="Apple-interchange-newline"><br></div></div><div>With my proposal you need to define A interfaces instead of AxMxN - A being the number of separate phases in validation - and reuse the same set of interfaces for all your classes and all your fields in a given project.</div><br></div></div></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; "><div style="word-wrap: break-word; "><div><blockquote type="cite"><div><div><div><div class="gmail_quote">@GroupSequence(value={Cheap.class,Expensive.class}, ordering=PER_TARGET)<br>public class DomainObject {<br><br> @Size(max=50, groups=Cheap.class) // constraint 1a<br> @Pattern(regexp="[a-z]*", groups=Expensive.class) // constraint 1b<br> private String name;<br><br> @Size(max=20, groups=Cheap.class) // constraint 2a<br> @URL(groups=Expensive.class) // constraint 2b<br> private String email;<br><br> @Size(max=100, groups=Cheap.class) // constraint 3a<br> @Pattern(regexp="[0-9]*", groups=Expensive.class) // constraint 3b<br> private String password;<br>}</div></div></div></div></blockquote></div></div></blockquote></div><br><div>From my understanding, if there is violation at size constraint of name field, email or passworld would not be validated? What I need is I want to validate all fields but for each field I would like to raise at most one violation an ordered way. For example, first size than pattern for name field. </div></span></blockquote></div><br><div>No, no, in my proposal, @GroupSequence.ordering=PER_TARGET means that this group sequence is applied per field and not globally. This is the behavior you are describing. For example, BV could return the following failures:</div><div><br></div><div>- name: size beyond 50</div><div>- email: not a url</div><div>- password: too long</div></body></html>