Saving object graph containing transient-new and attached objects

Question

Problem
We have simple FK relationship A->B relationship and create inside the transaction (service façade method) a new instance of A:
A a = new A().
Later in the same transaction we read independent instance of B from DB and put it in the ralationship with A:
a.setB(b);
Afterthat (in the same transaction) we want to save the object graphstarting with instance ‘a’. We do it with
pm.attachCopy(a);
We get an Exception:
<4|false|4.0.0EA5> kodo.util.UserException:
The instance "mypackage.A-pypackage.A-14638" is already managed.
FailedObject: mypackage.A - mypackage.A -14638 at kodo.jdo.PersistenceManagerImpl.processArgument(PersistenceManagerImpl.java:1259)
Known solution
Detach the instance ‘b’ before calling pm.attachCopy(a);
We could achieve this for example using Autodetach=commit and puting read and save operations in separate transactional methods (façade calls).
This solution is unsatifying, because we want to be able to manipulate object graph inside the transaction without caring explicitly about attach/detach semantic.
Question
We habe an heterogeneous object graph consisting of attached, detached and transient-new objects. How can we make the graph persistent with one API call on the roor object ?
Which mapping settings have to be done ? How KODO decides which object is ‘new’ and shhould be inserted and which obejct has to be updated ?

Answer 1

Denis,
Even the makePersistent (...) call is redundant but not harmful as long
as the instance is managed (and not detached).
Denis Sukhoroslov wrote:
Hi Andre,
Not clear, why do you call pm.attachCopy(a) at all. I haven't worked with
kodo 4.0 yet, but in 3.4.0 you just need to call pm.makePersistent(a). In
the same way you can persist whole object graph, AFAIK.
Denis.
"Andre Teshler" <[email protected]> wrote in message
news:[email protected]..
Problem
We have simple FK relationship A->B relationship and create inside the
transaction (service fa??ade method) a new instance of A:
A a = new A().
Later in the same transaction we read independent instance of B from DB
and put it in the ralationship with A:
a.setB(b);
Afterthat (in the same transaction) we want to save the object
graphstarting with instance ???a???. We do it with
pm.attachCopy(a);
We get an Exception:
<4|false|4.0.0EA5> kodo.util.UserException:
The instance "mypackage.A-pypackage.A-14638" is already managed.
FailedObject: mypackage.A - mypackage.A -14638 at
kodo.jdo.PersistenceManagerImpl.processArgument(PersistenceManagerImpl.java:1259)
Known solution
Detach the instance ???b??? before calling pm.attachCopy(a);
We could achieve this for example using Autodetach=commit and puting read
and save operations in separate transactional methods (fa??ade calls).
This solution is unsatifying, because we want to be able to manipulate
object graph inside the transaction without caring explicitly about
attach/detach semantic.
Question
We habe an heterogeneous object graph consisting of attached, detached and
transient-new objects. How can we make the graph persistent with one API
call on the roor object ?
Which mapping settings have to be done ? How KODO decides which object is
???new??? and shhould be inserted and which obejct has to be updated ?