[hibernate-issues] [Hibernate-JIRA] Commented: (HV-381) Provide a fail fast switch to stop processing constraints on first failure

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-381?page=com... ] Emmanuel Bernard commented on HV-381: ------------------------------------- another approach is to make maxFailure a method only available on the object returned by failFast. That way, people cannot get confused by what Gunnar is pointing out. WRT the last comment by Gunnar, I think that {code} final Validator validator = factory.unwrap( HibernateValidatorFactory.class ) .usingContext() .failFast( true ) .maxFailures(5) .getValidator(); {code} is more readable than {code} final Validator validator = factory.unwrap( HibernateValidatorFactory.class ) .usingContext() .maxFailures(5) .getValidator(); {code} We can even think about using failFast() instead of failFast(boolean) The drawback of that approach is that it's a bit harder on generic users of the programmatic API (ie the one having a failFast boolean). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira