I realize that after a childContext.commitChangesToParent(), the globalContext.uncommittedObjects() contains objects in
globalContext.
So at application level, based on the persistence state, I can add new objects and delete old objects in my lists
without localObject() conversion.
Thanks for y
Thanks Andrey,
context.uncommittedObjects() is a good idea.
I have also thought to get rid of child context and conversions using transaction when a session needs it . I will look
documentation about this ...
Regards
Pierre
- Original Message -
From: "Razumovsky Andrey" <[EMAIL
I haven't actually ever used the 'localObject' method. I mean you can work with nested context the same way as with
parent (global) one, i.e:
It seems to me that if you want to make relations between objects, they have to
be in the same context.
My idea is to have my list of objects in the pa
Thanks Andrey,
I am using what you propose for getting child context at session level
chidContext= globalContext.createChildDataContext();. But I dont understand
your sentence :
it collapses to just calling one method.
Do you mean using localObject to get object in globalContext ?
objectI
Hi,
I plan to have a list of DataObject in my application. At init, the list is loaded with the global DataContext
associated with application level.
At the session level, I will have a child DataContext so that objects can be created/updated/deleted without interfering
with others sessions u