|Re: [CDO] and eAdapters [message #1007228 is a reply to message #1007123]
||Tue, 05 February 2013 07:00
| Eike Stepper
Registered: July 2009
Everything you say seems totally correct. Adapters are generally a means to attach transient pieces of information
(e.g., UI components) to persistable objects and to receive change notification from these objects. A content adapter
uses these change notifications to react to containment changes (i.e., additions or removals of contained objects) to
attach/detach itself to/from subtrees.
Am 04.02.2013 15:37, schrieb Christophe Bouhier:
> Thanks for confirming it is not persisted, (The DB schema kind of gave it away already :).
> On the adapter lifecycle, well, just thinking out loud here. As you know I am messing around with the
> CDOLazyContentAdapter. Now calling adapt() will attach the adapter to eAdapters(). (Which doesn't make the object
> DIRTY I believe). I can imagine the adapter being auto-detached, when the state changes. So if an object becomes
> Perhaps this is the details of the implementation of the content adapter, considering it is updated when the object
> state changes.
> Cheers Christophe
Powered by FUDForum
. Page generated in 0.03089 seconds