[hibernate-issues] [Hibernate-JIRA] Updated: (HV-446) The annotation processor should allow constraint annotations at non-getter methods

[Gunnar Morling (JIRA)]

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

Gunnar Morling updated HV-446:
------------------------------

    Description: 
Currently the AP creates a compiler error if any non-getter method is annotated with constraint annotations. With the introduction of the method validation feature this check is no longer correct, the AP should allow constraints at any non-static, non-void method.

We might also introduce a processor option that controls, whether constraints at non-getters are allowed or not. That way users who don't work with method validation could keep the current behavior.

  was:
Currently the AP creates a compiler error if any non-getter method is annotated with constraint annotations. With the introduction of the method validation feature this check is no longer correct, the AP should allow constraints at any non-static method.

We might also introduce a processor option that controls, whether constraints at non-getters are allowed or not. That way users who don't work with method validation could keep the current behavior.


> The annotation processor should allow constraint annotations at non-getter methods
> ----------------------------------------------------------------------------------
>
>                 Key: HV-446
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-446
>             Project: Hibernate Validator
>          Issue Type: Improvement
>          Components: annotation-processor
>            Reporter: Gunnar Morling
>            Assignee: Gunnar Morling
>             Fix For: 4.2.0.CR1
>
>
> Currently the AP creates a compiler error if any non-getter method is annotated with constraint annotations. With the introduction of the method validation feature this check is no longer correct, the AP should allow constraints at any non-static, non-void method.
> We might also introduce a processor option that controls, whether constraints at non-getters are allowed or not. That way users who don't work with method validation could keep the current behavior.

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