[hibernate-issues] [Hibernate-JIRA] Commented: (HV-134) Built-in constraint parameter validation
Hardy Ferentschik (JIRA)
noreply at atlassian.com
Tue Sep 15 15:35:50 EDT 2009
[ http://opensource.atlassian.com/projects/hibernate/browse/HV-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33969#action_33969 ]
Hardy Ferentschik commented on HV-134:
--------------------------------------
Do you still prefer IllegalArguementException?
The spec says in 8.3 "When a constraint declaration is illegal, ConstraintDeclarationException is raised."
Adding a constraint to an entity including specifying the constraint attributes is in my eyes a "declaring a constraint". Hence I used ConstraintDeclarationException (admittedly not consistently yet). I need to make this consistent now and I am wondering if you changed your mind.
If this is not a case to use ConstraintDeclarationException - where do you use this exception then anyway?
> Built-in constraint parameter validation
> ----------------------------------------
>
> Key: HV-134
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-134
> Project: Hibernate Validator
> Issue Type: Bug
> Components: engine
> Affects Versions: 4.0.0.Alpha3
> Reporter: Emmanuel Bernard
> Assignee: Hardy Ferentschik
> Fix For: 4.0.0.GA
>
>
> When params are invalid (ie max < min), the ConstraintValidator raises a ValidationException.
> While not wrong from a spec POV, I don't think the impl has to use VE. It probably amkes more sense to use IllegalArgumentException
--
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