Michael Dick wrote:
>
> I think that's the solution that B.J. mentioned in the JIRA. The testcase
> attached to the JIRA might shed some light on the problem. Is there
> anything
> obviously different between that testcase and what you're doing?
>
I didnt studied the testcase exactly.
I notice that I have the same kind of dependency twice at my application and
one works and the other dont.
Snippet of the working dependency:
@Table(name = "person")
@Entity
public class Person {
@ManyToMany(cascade = CascadeType.REFRESH, fetch = FetchType.EAGER)
@JoinTable(name = "titelzuordnung", joinColumns = { @JoinColumn(name =
"person") },
inverseJoinColumns = { @JoinColumn(name = "titel") })
private List<Titel> titelListe;
..
}
table:
person --n:m-- titel with jointable titelzuordnung which just contains the
both foreignkeys as primarykeys.
Snippet of the not working dependency:
public class EuFeuerwaffenpass {
@ManyToMany(cascade = CascadeType.REFRESH, fetch = FetchType.LAZY)
@JoinTable(name = "eufeuerwaffenpasszuordnung", joinColumns = {
@JoinColumn(name =
"eufeuerwaffenpass") }, inverseJoinColumns = { @JoinColumn(name =
"waffe") })
private List<Waffe> waffeListe;
...
}
table:
eufeuerwaffenpass--n:m--waffe with jointable eufeuerwaffenpasszuordnung
which just contains the both foreignkeys as primarykeys.
--
View this message in context:
http://openjpa.208410.n2.nabble.com/WAS7-persistence-provider-problems-openJPA-Hibernate-tp5514291p5514754.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
