[
https://issues.apache.org/jira/browse/OPENJPA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972175#action_12972175
]
Kevin Sutter commented on OPENJPA-1607:
---------------------------------------
Hmmm... I just looked at our junits for this scenario and we have several
tests that show that this works. The test cases are:
o TestContainerSpecCompatibilityOptions
o TestSpecCompatibilityOptions
And, the corresponding entity definitions are:
o Uni_1ToM_FK
All of the code and testcases were integrated via OPENJPA-1253. And, the
version references you have provided seem to indicate that you are running with
this code base.
>From what I can tell, these tests are using the same mechanisms that your
>tests are expecting. Maybe you can review the OpenJPA tests to see how they
>might differ from your scenarios?
In the mean time, I will continue to investigate as well. Thanks.
> 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.
