Hi,

I have a case that could be described as follows:

Object A has a List of B's.
Each B has a List of C's.

I cannot successfully map the entire relationship.

I have been able to do map and persist the A-to-B relationship by including a <list>, <key>, <index> and <composite-element> in A's <class> area.

To map the B-to-C relationship, I tried to include a <list> for C in B's <composite-element> area. For C, I identitifed two key columns, a_id and b_id, and an index c_pos.

Hibernate flagged the <list> as an invalid token within <composite-element>.

Looking at the documentation, and at the complaint from Hibernate, it appears that <nested-composite-element> may come into play. But I will be darned if I can find any documentation or examples of this on the web.

(As a side note, I have been able to successfully persist this type of relationship(s) using Sets, but the client-side programmers are insistant on using Lists in this case.)

What do I need to do? (Or where can I go to find the info?)

I can provide more detailed info if needed (i.e. class, maps, schema).

Thanks so much!

Brian Kuhn

Have you read http://www.hibernate.org/hib_docs/reference/html/parent-child.html ? I don't see the need to use composite-element in this case. Note however that lists are not officially supported for bidirectional one-to-manys. There are workarounds, search the forum.

You can't map it as a composite-element, composite-element does not support one-to-many association to other elements.
Map it using an entity