This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
Um, my solution is using EJB3 and Hibernate. Check out the documentation on mapping Many to Many.
Joined: Aug 11, 2006
Hi, In fact, the annotation @ManyToMany does not function for my case, because my table WASNMI is not simply a table of joint, but it contains of another fields that the foreign keys.
I implemented as follows:
TermSource and SnomedInter must have a collection of TermProj, and not of TermProPK. In the same way, TermProj must only have a direct bond towards 1 TermSource and 1 SnomedInter in addition. It is HIBERNATE which is given the responsability to manage the keys themselves! Us, only the objects are managed.
it remains me to be known how I can reach a SnomedInter object to leave a TermSource object!! I tested implementer as follows:
[ November 17, 2006: Message edited by: Dupon David ]
[ November 17, 2006: Message edited by: Dupon David ] [ November 17, 2006: Message edited by: Dupon David ]
You keep looking for an answer, but you don't seem to be paying attention to the answers you are getting. You certainly didn't seem to even look past the basic chapter on OR mapping in our JPA book. Take a look in Chapter 8. There is a "Mapping Relationship State" section there that discusses your exact association table situation.