I think I have this one traced down and I would like some comments. I
have a one-to-many-to-many and the last 'many' can belong to multiple
(2) instances. So when the first deletion of the last class happens, the
entry.status = DELETED in Session.java. The second time it comes around
it hits this line:
if (entry.status!=LOADED) throw new ObjectDeletedException("Object was
already deleted", entry.id);
Which is where I get my error. When I comment out that line I get in an
infinite loop. Is there a work-around for this scenario? Thanks.
Matt
-----Original Message-----
From: Matt Dowell
Sent: Monday, February 10, 2003 2:04 PM
To: '[EMAIL PROTECTED]'
Subject: cirrus.hibernate.ObjectDeletedException: Object was already
deleted: 32
I am getting this error in my test. Here is what I have
1) I have a one-to-many and the many has a one-to-many. Three entities
all linked.
2) cascade="all"
3) I can create the objects, with the relationships just fine.
4) When I load an object (the one) and call session.delete(oneObject) I
get this error:
cirrus.hibernate.ObjectDeletedException: Object was already deleted: 32
5) The '32' I think is the ID of the last MANY class..
Any ideas? Thanks,
Matt Dowell
Notiva Corp.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
