Create an PrivilegeId class that encapsulate the ids. Make that class @Embedded and put it in the Privilege with @EmbeddedId In the PrivilegeId class, put an @OneToMany to the Profile and the privilege id.
Create an PrivilegeId class that encapsulate the ids. Make that class @Embedded and put it in the Privilege with @EmbeddedId. In the PrivilegeId class, put an @OneToMany to the Profile and the privilege id.
The first part is what I did. The Profile is OneToMany to the Privilege. Not the other way.
The join is only on the profile_id. – MeBigFatGuy Dec 28 '10 at 22:03 What is ProfilePrivilegeEO? Put the @JoinColumns annotation and use the two @JoinColumn there.
This does not affect the generated schema negatively, because in the @OneToMany, the key is in the foreign class, the Privilege (exactly where it is actually and should be). – Victor Dec 28 '10 at 22:58 ProfilePrivilegeEO is the entity for the Privilege table. I don't have two @JoinColumns to specify from the Profile class, as it doesn't know about privileges.
That is the problem. – MeBigFatGuy Dec 29 '10 at 1:15.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.