openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Bauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-1607) Using unidirectional one-to-many target foreign key throws exception
Date Thu, 16 Dec 2010 21:17:00 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972211#action_12972211
] 

Jeremy Bauer commented on OPENJPA-1607:
---------------------------------------

IIRC, the reason this new behavior wasn't simply enabled in OpenJPA 2.x.x, regardless of persistence
version, is that it caused issues when running some JPA 1.0 TCK variations.  With the exception
of the API signature tests, we made it a priority to make sure all of the 1.0 variations passed
with 2.x.x level code to help ensure backward compatibility.

> Using unidirectional one-to-many target foreign key throws exception
> --------------------------------------------------------------------
>
>                 Key: OPENJPA-1607
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1607
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.0.0-beta3
>            Reporter: Oliver Ringel
>         Attachments: openjpa-1607.tar
>
>
> Using this simple unidirectional relationship
> @OneToMany
> @JoinColumn(name = "DEPARTMENT_ID")
> private Set<Employee> employees;
> causes to the following exception
> <openjpa-2.0.0-beta3-r422266:926797 fatal user error> org.apache.openjpa.persistence.ArgumentException:
You have supplied columns for "com.example.Department.employees", but this mapping cannot
have columns in this context.
> Unidirectional one-to-many target foreign key relationship should be supported in JPA
2.0.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message