I am storing my associations as Maps. I only saveOrUpdate on the parent Object. I cascade updates. When I want to create a new child Object, I simply put it in the map of the parent Object. The id for the new child Object is set using a database sequence, so I never explicitly set the id of the child Object.

When I try to create a single new child Object, it works fine. When I try and add multiple new child Objects it doesn't work at all.

I am assuming the problem has something to do with all of the child Objects having the same, null, id which is used as the key in the Map.

Could anyone shed some light on this situation? How do I persist multiple new child Objects by adding these new child Objects to the Map of the parent Object and calling saveOrUpdate on the parent?

Hi

in the map tag should do the job.

HTH
Ernst

Hello, thank you for responding.

I already cascade="all-delete-orphan", so that isn't the problem. When I only add a single new Object (no id) to the Map and saveOrUpdate the parent Object, the new child object that I stored in the Map persists to the database fine and is assigned a new id off the database sequence. The problem happens when I try to add more than one new child Object to the map and persist the parent Object. When I do this, none of the new child Objects persist back to the database.

Any other ideas?

Tom,

>> I am assuming the problem has something to do with all of the child Objects having the same, null, id which is used as the key in the Map.<<

I had a similar problem but with sets, where my equals() and hashcode() were based on a database-generated key. This breaks the set contract, causing all sorts of pain (none of it Hibernate's fault).

Solution was to set a generated (private) GUID in the constructor, and base equals() and hashcode() on this, making my sets stable and allowing all my business properties to be mutable. I still use a sequence for the database ID.

John