[
https://issues.apache.org/jira/browse/OPENJPA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852394#action_12852394
]
Oliver Ringel commented on OPENJPA-1607:
----------------------------------------
Hi Thomas,
sorry, but I have to disagree. Using a jointable ist default behaviour if you
not use @JoinColumn,
but the JPA 2.0 spec also supports unidirectional one-to-many relationships
without the need of jointables.
See section 11.1.21 JoinColumn Annotation of the JPA 2.0 spec.
The RI supports this kind of relationships.
> 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.
