|
Re: TransactionChangeRecorder not added in my CDOObject adapters [message #1774603 is a reply to message #1774515] |
Tue, 17 October 2017 17:06 |
|
Hi, Arthur,
The `TransactionChangeRecorder` should have discovered the new object automatically when it was added to its container, assuming that the container has it attached. If notification is disabled on that container when your object is added, then there's no way for anything, even this change recorder, to know about it. Is that what's happening?
I'd suggest debugging the addition of your object to its container to see what's going on there.
HTH,
Christian
|
|
|
|
|
|
Re: TransactionChangeRecorder not added in my CDOObject adapters [message #1774699 is a reply to message #1774686] |
Wed, 18 October 2017 17:22 |
|
Hi, Arthur,
It can be difficult to pinpoint where exactly in what EList implementation an object is added to a list. It is easier when debugging a problem like this to add an override of the eBasicSetContainer(...) method in the XyzImpl class that you're attaching to the model and a breakpoint on the super(...) call. No matter what else happens, and CDO has some weird ways of materializing objects in a model out of the ether, the EMF run-time has to ensure that the object is assigned its container.
HTH,
Christian
|
|
|
Powered by
FUDForum. Page generated in 0.04533 seconds