[hibernate-issues] [Hibernate-JIRA] Resolved: (HV-535) Validator sees all nulls on proxy object when proxied entity class has constraint annotations applied to fields instead of methods

[Hardy Ferentschik (JIRA)]

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

Hardy Ferentschik resolved HV-535.
----------------------------------

    Resolution: Won't Fix

Not much we can do in this case. When dealing with proxies it is always better to use getters. There is no way to intercept access to fields.

> Validator sees all nulls on proxy object when proxied entity class has constraint annotations applied to fields instead of methods
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HV-535
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-535
>             Project: Hibernate Validator
>          Issue Type: Bug
>    Affects Versions: 4.1.0.Final, 4.2.0.Final
>         Environment: RHEL 6.1
>            Reporter: Jesse Hutton
>
> When hibernate creates a proxy of an entity relation (eg. when FetchType.LAZY is specified on a @ManyToOne relationship) and the Bean Validation annotations have been applied on the proxied class to fields instead of methods, the validator can't see any values. All it sees are nulls.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira