[hibernate-issues] [Hibernate-JIRA] Resolved: (BVAL-99) Implement type-safe ConstraintValidator resolution mechanism

[Hardy Ferentschik (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/BVAL-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hardy Ferentschik resolved BVAL-99.
-----------------------------------

    Resolution: Fixed

implemented first cut for alpha release

> Implement type-safe ConstraintValidator resolution mechanism
> ------------------------------------------------------------
>
>                 Key: BVAL-99
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-99
>             Project: Bean Validation
>          Issue Type: New Feature
>          Components: ri-general
>            Reporter: Emmanuel Bernard
>            Assignee: Hardy Ferentschik
>
> I did implement the embryo that determine the type of a given ConstraintValidator
> See ValidatorTypeHelper class and its test.
> With this type, the algo needs to find the best matching ConstraintValidator for a given declaration.
> Here is a proposal:
> For a given type T when a constaint is applied,
> List all CV whose type U is such that U.isAssignableFrom(T) is true
> then for each element U of this list:
>  - if another element in the list is such that U.isAssignableFrom(V), remove U
> if there is more than one remaining element => raise the AmbiguousException
> Also when a Constraint is analyzed, if 2 CV target the same type, an exception should be raised.

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