[
http://opensource.atlassian.com/projects/hibernate/browse/HV-256?page=com...
]
Jaro Kuruc commented on HV-256:
-------------------------------
I just realized translations for the following message keys would not be ideal in case
exclusive attribute is set to true.
javax.validation.constraints.DecimalMax.message=must be less than or equal to {value}
javax.validation.constraints.DecimalMin.message=must be greater than or equal to {value}
The ' or equal to' part would have to be conditional, meaning there would have to
be two message variants for each of the keys. In the implementation,
ConstraintValidatorContext would probably have to be used to build constraint violation.
Any other ideas?
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira