I have a table structure like the following:

Organization -- > OrganizationAddresses < -- Address



I have and Organization object which has a mapped many to many relationship using the bag construct to organization addresses. When I try to delete an address from the organization's address list then consequently delete the address itself, I receive the following error message from hibernate and my transaction rolls back.


"Flush during cascade is dangerous - this
might occur if an object was deleted and then re-saved by cascade".


I am stumped on how to solve this problem. Do I have to delete the actual Address object in a separate hibernate transaction?

Any ideas well appreciated.


Shon

Does the hibernate FAQ applies to you ?

Does the 8th chapter of Hibernate reference guide help ?

Thanks for the reply!

Yes, actually it does. I found the problem shortly after posting my question. It turns out that the object that was causing the problem had a problem with the equals implementation which was causing a removal from the collection never to happen. Thus the error.

Thanks for your reply!

Shon

Could tell me what you do for this problem in detailed?

Thanks, I met a same problem!