Looking at section 18.1 of the manual... Could someone please show what the mapping for the Employer and Employee objects might be if they both had a collection of Employment objects?

Thanks, Will

Well, there are really a lot of mapping examples out there, for example in the hibernate tutorial list http://www.hibernate.org/78.html#A3. I am really to lazy to do handholding for your case, perhaps somebody else is not ;)

Well, I actually have been working hard to understand the mappings on my own. What I haven't found is enough examples of bidirectional many-to-many mappings where the relationship is an entity class. The Employer/Employee example is perfect for this if an Employment collection is added to Employer and to Employee.

I have a similar question about the Custoomer/Order/Product example, if Product had a collection of LineItem objects (an odd example, but still...)

I'll drive you, but in exchange, you'll create a wiki page for that after testing it, good deal, no ? :)

Actually it's the same as if there were a simple one-to-many, many-to-one links.



Same for the other side.

For Customer/Order/Product, you can't do it using a composite-element, composite-element are only related to it's father. So you need to replace composite-element by an Entity.

It's a deal, Emmanuel. I'll work with this today and write something up.
Thanks.

Will

Don't hesitate to post again if you have problems, we are not that lazy after all :) You just get better results in general if you try to work yourself into it and just post if you run into problems.