title: It's so confused with the Hibernate Validator @Email constraint
body: <p>I want to validate step by step, that is to say, if one constraint is falied, the next one will not be check, I defined the constraints in model like this:</p>
  
  <pre><code>@NotEmpty
  @Size(min = 4, max = 40)
  private String password;
  
  @NotEmpty
  @Email
  private String email;
  </code></pre>
  
  <p>for the two properties, the validate result is different, if the password is empty, the error print is :</p>
  
  <pre><code>Password cant be empty
  Password must be between 4 and 40 characters
  </code></pre>
  
  <p>but for email, the error print is :</p>
  
  <pre><code>Email cant be empty
  </code></pre>
  
  <p>for the email, the result is what I want, but I didn't know what's the difference between the @Email constraint and others, if there have some especial handler for the @Email constraint in the hibernate internal code?</p>
  
  <p>I want validate step by step, but I didn't find out a perfect approach, the @GroupSequence also isn't a good scheme, I found the @Email have the feature, but I didn't know why @Email perform so especial.</p>