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

[Gunnar Morling (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HV-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39905#action_39905 ] 

Gunnar Morling commented on HV-381:
-----------------------------------

Ah ok, now I see. Making maxFailures only available when failFast() was called, seems like a good approach. 

Continuing Emmanuel's last idea we might also offer simply two overloaded methods, failFast() and failFast(int maxFailures), where there first would be equivalent to calling failFast(1). This would allow to set the maximum failure count with one call, which I personally would prefer. But I'm fine with either way as long as there is no chance to use the API in a wrong way :)

> Provide a fail fast switch to stop processing constraints on first failure
> --------------------------------------------------------------------------
>
>                 Key: HV-381
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-381
>             Project: Hibernate Validator
>          Issue Type: Bug
>          Components: engine
>    Affects Versions: 4.1.0.Final
>            Reporter: Emmanuel Bernard
>            Assignee: Kevin Pollet
>             Fix For: 4.2.0.Beta2
>
>
> On first failure, HS should stop processing constraint failures and return straight.
> This should be both a {{ValidatorFactory}} setting and a {{Validator}} setting.

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira