I have a piece of code which has a set with a cascade="all-delete-orphan". But as soon as I add a sort="Comparator" the cascades stop working.
The cross reference gets set to null and orphans are not deleted.

It works fine without the sort on the set!??

I tried a work arround with the comparator in the setter or getter creating
a new collection and sorting but this does not work as you are not allowed to dereference a collection with "all-delete-orphan". Is this a bug or am I doing something wrong!

Mapping:

<class name="com.core.risk.Control" table="Control">
<cache usage="read-write"/>
<id name="id" type="long" column="controlId" unsaved-value="-1">
<!--Hibernate Unique Key Generator-->
<generator class="sequence">
<param name="sequence">HIBERNATE_SEQ</param>
</generator>
</id>
<property name="description" column="description" type="com.riskgovernance.dao.hibernate.LongStringType"/>
<property name="name" column="controlName" type="string"/>
<property name="cost" column="cost" type="double"/>
<one-to-one cascade="none" name="baseCost" outer-join="true" access="field" />
<set name="auditData" table="AuditData" cascade="all-delete-orphan" sort="com.core.AuditDataComparator">
<key column="objectId"/>
<one-to-many class="com.riskgovernance.core.AuditData"/>
</set>
</class>

Sorry my mistake just discovered it was because I was sorting by date and
never returned 0 from comparator. to avoid losing duplicates and this obviously fails when hibernate tries to remove the object from the collection.