The problem is a bit strange. I have a two types of items, categories and products.

* A category has a set of products assinged using addProduct/removeProduct.
* A product has a parent category (stored as category_fk).

The failing example:
Having a single Category and a single Product:

*add the category
*add the product (all done by using storeOrUpdate to get an id for both)

*set product's parent category to category. (the Product.setCategory calls Category.addProduct() to update the category's set of products)

*flush this.

This works well. But when the testcase tears down, it throws an exception. While tearing down, the test case removes all categories and products by issusing delete(""FROM object IN CLASS "+clazz.getName()). The hibernate exceptions says, the given row was not found in the table. So I guess the collection didn't got updated or something.

So my questions goes:

How are mappings such this normally implemented? I am wondering, cause while adding a product to a category, I also set the parent of the child manually. Is this a normal way to get the job done?

Does anybody knows a good example of a working child parent relation (mapping+source for hibernate 2.1.2).

Does anybody knows, what might cause the problem? I think about the cascading effects?!

Here is the mapping section for the relation:

{category.getProducts}
<set name="products" lazy="true" inverse="false" cascade="delete" sort="unsorted">
<key column="CATEGORY_FK"/>
<one-to-many class="org.ocsn.domain.Product" />
</set>

{product.getCategory}
<many-to-one name="category" class="org.ocsn.domain.Category" cascade="none" outer-join="auto" update="true" insert="true" column="CATEGORY_FK"/>

Please have a look at
The parent child relationship chapter
and http://www.hibernate.org/155.html
Your inverse="true" choice may be broken.

+ did you commit the changes