I know this has been discussed couple times, but I still have one simple question:

What should I do to make Hibernaye deassociate object instead of throwing this exception (net.sf.hibernate.ObjectDeletedException: deleted object would be re-saved by cascade (remove deleted object from associations): 2273119, of class: com.exigen.ipb.policy.infrastructure.QuoteSummaryJDO)?

I was thinking that setting cascade to "all" whould help but it is not helping. I am still getting same exception. Also as I understand "all" means that all children will be deleted when parent is deleted???

Rihards

The problem is that you resave a deleted object.
Check your object graph and remove the deleted objects from the whole graph

Hi!
I've the same problem...any hints here?
Thanks in advance.

That probably means that the object you are trying to delete is a child of some other collection. Setting up cascade="all" for the object means that its children would be deleted/updated automatically unless they don't belong to some other parent.

you have to remove the object you are trying to delete for its parent collection.

...FROM its parent collection

Example:

..............
objectBeingDeleted.getParent().getChildren().remove(objectBeingDeleted);
..............

and then you can do
.......
session.delete(objectBeingDeleted
.......

I'm having the same problem and I am removing the child object from the parent collection.

The code --


The tx.commit() throws the exception. Team is mapped as follows --

After the exception is thrown, the row in the player table has teamid set to null. However, my expectation is that it would have been deleted since it's now orphaned.

Any help here? Thanks!![/code]

This is a real problem if we need to move children from one object to another.

We have a feature that split an object into more objects. Therefore, we need to create a new object and move some of the children from the original one to the new one. We don't have any solution but clone the children and delete the original copy of the children.

you can avoid using delete orphan

I'm upgrading from 3.1.3 to 3.2.0 and I just started getting this problem.

Its true that the stuff I'm deleting is in collection already, but version 3.1.3 and earlier never gave me this problem, and everything worked (or at least Hibernate never throw this exception, still have to confirm did it actually work or not).

What changed since 3.1.3, and how to best fix all this? Was cascade checking improved and therefore I get an exception now or did the behavior change?

I'm wondering if this has anything to do with new argument (transientEntities) in cascadeBeforeDelete() and cascadeAfterDelete() in DefaultDeleteEventListener (I have an event listener that extends it). What is it used for and what, if anything, am I supposed to be passing there?

Dynamo92, try doing:

for (Iterator ip = team.getPlayers(). iterator(); ip.hasNext();) {
Player player = (Player) ip.next();
if (player.getName().equals("Open")) {
Transaction tx = hibSession.beginTransaction();
ip.remove();
//hibSession.save(team);
hibSession.delete(player);
tx.commit();
continue;
}
}

And see if it works.

I just went through my integration and HTML test, and its definitely the case that I was doing this before and it was working fine (I was deleting objects with Session.delete() while they were in some collection), and this is now throwing exception all over the place for me.

Could someone from Hibernate team explain what changed between 3.1.3 and 3.2.0?

I'm using Hibernate 3.2. The way my app works is that I evict the parent object from the current Hibernate session; the subsequent deletion of the child object works fine (removing the child from a parent set will synchronize the foreign key to null, and most schemas will break when this occurs). The only thing you may have to be wary of is preloading the sets for the parent, since by default 3.2 lazy load is true. This can be done by invoking Hibernate.initialize on the collection (e.g., Hibernate.initialize(parent.getChildren())), usually in the DAO layer.

This helped me solve the problem of moving a child from one parent to another.

I don't understand why all-delete-orphan was not appropriate though.
Could you please explain me why? Or point me to reference/book page?

thanks

I had a similar problem.
My situation is the following: i have two entity (Candidate and Job) and a many to many relation between them (Candidacies).
To delete an instance candidate of the entity Candidate:

1. I have got the candidate
2. I have cleared the elements of the list that represents the relations with one or more jobs
3. I have made persistent the candidate
4. I have removed succesfully the candidate

Here is my code:

I hope this helps someone
Best regards
Giordano