Best of Xebia tech list: Hibernate Cascade Question

21 Sep, 2007

I am sorry I am a bit behind on posting the techlist questions, but I have been a bit busy lately with tons of different projects.
This time we have a hibernate question..

SubjectHibernate question
DateAugust 27, 2007 16:30:26

I have a Hibernate question. This is the situation (I ommited rest of annotations etc):
[java]class Organisation {
private List allContactDetails;
class AbstractContactDetails {
It is a uni-directional one to many.
Now I want to delete the Organisation and that should cascade to the allContactDetails. That's why I added the Hibernate specific annotation "@Cascade(org.hibernate.annotations.CascadeType.DELETE_ORPHAN)". In my test code I then do:
(The flush is there so I can test after the last call as Hibernate only synches with the database with an explicit flush or a select).
This results in the following exception:
Caused by: org.hibernate.HibernateException: A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance: domain.Organisation.allContactDetails
I found that a bit strange because I think this is the whole idea behind the all-delete-orphan thing.... I am adding it so Hibernate deletes my orphans and now it complains that it is no longer referenced... Any idea's?
We are using Hibernate and Java 5.

FromSilvester van der Bijl
SubjectRE: Hibernate question
DateAugust 27, 2007 16:33:19

As far as I know you shouldn't set the collection to null. Does it work when you just clear the list? Don't now how Hibernate handles this, but I'm guessing it needs a reference to the collection to be able to detect which items should be deleted (the orphans).

FromLars Vonk
SubjectRE: Hibernate question
DateAugust 27, 2007 16:38:06

Great, thanks Silvester that indeed solved it.

Explore related posts