Re: StateManager savedImage retains references - not the original values


It knows what to update based on what methods the user calls on the collection/map. Take the example of a field of type Collection, using

The user does an "add" of an element, so calls

If using optimistic txns (i.e delaying sending updates to the DB til required) it is a "queued update", so it calls
ownerSM.getExecutionContext().addOperationToQueue(new CollectionAddOperation(ownerSM, backingStore, element));
and otherwise (sending updates to the DB immediately) it calls backingStore.add(ownerSM, element, useCache ? delegate.size() : -1);

But then that is the whole point of using a proxy, I see no need for "change tracking" as such, until a problem exists that requires it.

Join to automatically receive all group messages.