[hibernate-issues] [Hibernate-JIRA] Commented: (HV-381) Provide a fail fast switch to stop processing constraints on first failure
Gunnar Morling (JIRA)
noreply at atlassian.com
Wed Feb 9 15:32:05 EST 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HV-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39899#action_39899 ]
Gunnar Morling commented on HV-381:
-----------------------------------
I'm not sure whether I like this as it leaves space for inconsistent invocations of the API such as
{code:java}
final Validator validator = factory.unwrap( HibernateValidatorFactory.class )
.usingContext()
.failFast( false )
.maxFailures(5)
.getValidator();
{code}
Plus, would it be sufficient to invoke maxFailures() or would it be required to invoke failFast() as well? If you don't feel like starting with the numeric parameter in the first place we should better leave it out at all.
> 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
More information about the hibernate-issues
mailing list