Change By:

Gunnar Morling (07/Jan/13 7:51 AM)

Description:

Currently the concerned constraint is not considered when determining the identity of {{ConstraintViolationImpl}} ({{equals()}} and {{hashCode()}}). This causes only one violation to be contained in the set returned by {{Validator#validate()}} when validating e.g. the following property:

{code}
@Size(min=2, message="must be 2 at least")
@DecimalMin(value="2", message="must be 2 at least")
String name = "1";
{code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira