| [CDO] and eAdapters [message #1007073] |
Mon, 04 February 2013 05:51  |
Eclipse User |
|
|
|
Hello,
Quick question, Are adapters added to a CDO object eAdapters() collection persisted?
If not, what would be the lifecycle for them in relation to the CDOState of the object?
Thanks Christophe
|
|
|
|
|
| Re: [CDO] and eAdapters [message #1007228 is a reply to message #1007123] |
Tue, 05 February 2013 02:00  |
| Eclipse User |
|
|
|
Hi Christophe,
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.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 04.02.2013 15:37, schrieb Christophe Bouhier:
> Eike,
> 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
> TRANSIENT.
> 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.03703 seconds
Home
.