Description Austin Teng 2010-05-19 10:51:50 EDT

Build Identifier: 20100218-1602

The attached test code (HibernateStoreBidirectionalTest.zip) produces an exception (NonUniqueObjectException.txt) when attempting to save the model to a CDO Server configured to use a Hibernate Store.  The code is built against a January 18th nightly, fairly close to the head of the "Root_branching" branch.

The problem seems to be with references that introduce cycles in the object graph.  If multiple objects in the committed change sub-graph reference a common object, Hibernate will produce a NonUniqueObjectException while attempting to lazily initialize the second copy of the shared object during a saveOrUpdate operation.

The problem can be avoided by taking the following actions:

1. Make sure the following property is *NOT* set:

<property name="teneo.mapping.cascade_policy_on_non_containment" value="PERSIST,MERGE"/>

This will avoid calling persist or merge on related objects that should be unaffected by changes to the initial object.  For example, if A references B, and A is changed, B should remain unaffected.

2. Using the merge operation instead of saveOrUpdate in the write operation of the HibernateStoreAccessor (HibernateStoreBidirectionalFix.patch).  This appears to work, however, I'm unsure if there are more subtle consequences to the approach I've taken.

Reproducible: Always

Steps to Reproduce:
1. Launch a CDO Server locally that is configured with the following options:
   - Hibernate Store
   - Teneo dynamic mapping provider
   - HSQLDB (any database works, but this is easiest)
2. Disable the cascade policy property (see description) in the CDO Server config
   - Leaving it enabled will trigger a different failure point caused by the bidirectional reference between Student and School
   - Disabling it triggers a failure caused by the reflexive "sibling" relationship
3. Run the unit test included in the attachments