Title: RE: Dependents in 1-N don't go away
I
understand. You have removed the DO from the parents list, but
you
have
not removed the DO from the database. This is because you
did
not
call the removed method of the DO. Try:
getDependents().remove(dependent); // remove DO from parent's
Title: RE: Dependents in 1-N don't go away
Is
that remove() method an abstract method to be implemented in the DO? they
inherit Object and the only required method to implement on them is the
deepCopy(), I don't see where the remove() method is or come
from.
Since
they are Depedent
Title: RE: Dependents in 1-N don't go away
You
may want to look at 9.4.4.2 in the proposed final draft which defines
the
remove() function of a DO. I don't have PD1 to tell you what
section it is there.
-tim
-Original Message-From: Christian Billen
[mailto:[EMAIL PROTECTED
I had the same problem with collections and it seems like a bug in Orion.
In some strange way, orion doesn't regard the dependent class in the
collection as the same as the incoming one, in spite that it is the same
type. I tried the getClass() method and it returned the same class name
Title: RE: Dependents in 1-N don't go away
Dependent objects (DO) do not go away automatically.
There is an un-implemented option in the deployment
descriptor called cascade-delete, but alas, it is
unimplemented.
The DO life-cycle is one of the main issues with DOs
in the spec and one
Title: RE: Dependents in 1-N don't go away
Hi
Tim, thanks for the info, by my problem is different
my
issue is I want to remove a dependent from the java.utill.Set in its parent
object and that if I call getDependents().remove(dependent) from the parent
object the dependent doesn't go away
