[hibernate-issues] [Hibernate-JIRA] Updated: (HV-305) JPATraversableResolver tries to access properties that do not exist

[Hardy Ferentschik (JIRA)]

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

Hardy Ferentschik updated HV-305:
---------------------------------

    Fix Version/s: 4.1.0
      Component/s: engine

> JPATraversableResolver tries to access properties that do not exist
> -------------------------------------------------------------------
>
>                 Key: HV-305
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-305
>             Project: Hibernate Validator
>          Issue Type: Bug
>          Components: engine
>    Affects Versions: 4.1.0.Beta1
>         Environment: Hibernate Validator 4.1.0.Beta1, Hibernate 3.5.0-Final
>            Reporter: Stephan Bublava
>            Assignee: Hardy Ferentschik
>             Fix For: 4.1.0
>
>         Attachments: validation-test.zip
>
>
> Prerequisites:
> - two entities that model a bidirectional 1:n relationship
> - both have class-level constraints
> - the collection that represent the n-side of the relationship is annotated @Valid
> - Hibernate 3.5 is in the class path
> In this case, validation of the entity that represents the 1-side fails, because JPATraversableResolver attempts to access a property that doesn't exist. (It looks for the collection in the wrong entity.)
> Changing any of the last three conditions makes the problem disappear...
> I've attached a test-cases that demonstrates this issue in more detail.

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