[hibernate-issues] [Hibernate-JIRA] Resolved: (HV-299) Annotation processor should check constraint annotation type declarations

[Gunnar Morling (JIRA)]

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

Gunnar Morling resolved HV-299.
-------------------------------

    Resolution: Fixed

Implemented the following checks:

* Retention policy must be RUNTIME
* Target must not be empty
* A validator must be specified (unless constraint is composed)
* Constraint must define members message, groups, payload with appropriate types and default values

Currently *not* implemented is a check, that in case the checked constraint is a composed one there is at least one common type supported by all composing constraints. This would be marked as error when using the constraint, though.

> Annotation processor should check constraint annotation type declarations
> -------------------------------------------------------------------------
>
>                 Key: HV-299
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-299
>             Project: Hibernate Validator
>          Issue Type: New Feature
>          Components: annotation-processor
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Gunnar Morling
>            Assignee: Gunnar Morling
>             Fix For: 4.2.0
>
>
> When visiting a custom constraint annotation type declaration, the AP should check the following:
> * proper declaration of groups(), message(), payload()
> * retention policy is RUNTIME
> * array of supported types must not be empty

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