[jira] Updated: (BVAL-21) ConstraintViolations set should not have duplicates and should store ElementType and use it in equals()

["Carlos Vara (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BVAL-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlos Vara updated BVAL-21:
----------------------------

    Attachment: bval-core.patch
                bval-jsr303.patch

Patches for bval-core and bval-jsr303 attached.

Added equals() and hashCode() methods in ConstraintViolationImpl.
Added getAccess() method in the signature of ValidationContext to allow access to it when building a new ConstraintViolation.

2 more TCK tests pass.

> ConstraintViolations set should not have duplicates and should store ElementType and use it in equals()
> -------------------------------------------------------------------------------------------------------
>
>                 Key: BVAL-21
>                 URL: https://issues.apache.org/jira/browse/BVAL-21
>             Project: BeanValidation
>          Issue Type: Bug
>          Components: jsr303
>    Affects Versions: 0.1-incubating
>            Reporter: Carlos Vara
>         Attachments: bval-core.patch, bval-jsr303.patch
>
>
> The returning set of ConstraintViolations should not have duplicate entries, so equals must be defined in ConstraintViolationImpl.
> Also, two ConstraintViolations with all equal fields except the way they access the property should be considered different, so ConstraintViolationImpl should store the ElementType and compare it in the equals() method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.