[hibernate-issues] [Hibernate-JIRA] Commented: (HV-256) Add 'exclusive' boolean attribute to @DecimalMin/@DecimalMax constraints

Hardy Ferentschik (JIRA) noreply at atlassian.com
Tue Nov 3 06:03:57 EST 2009


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

Hardy Ferentschik commented on HV-256:
--------------------------------------

Yes, this would require two messages per constraints. Via ConstraintValidatorContext you could indeed change the used message template depending on the 'exclusive' attribute. 
However, a change in the spec for @DecimalMin/@DecimalMax is not happening anymore at this stage of the game. The only other alternative would be to have Hibernate Validator specific @DecimalMin/@DecimalMax constraints under a different package. Not really something I fancy at the moment.

> Add 'exclusive' boolean attribute to @DecimalMin/@DecimalMax constraints
> ------------------------------------------------------------------------
>
>                 Key: HV-256
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-256
>             Project: Hibernate Validator
>          Issue Type: Improvement
>          Components: validators
>    Affects Versions: 4.0.0.GA
>            Reporter: Jaro Kuruc
>         Attachments: patch.patch
>
>
> Please find attached implementation and tests for a suggested improvement to @DecimalMin/@DecimalMax constraints.

-- 
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