- We have introduced
org.eclipse.emf.common.util.DelegatingEList,
org.eclipse.emf.common.notify.impl.DelegatingNotifyingListImpl, and
org.eclipse.emf.ecore.util.DelegatingEcoreEList to allow clients to wrap an
existing list implementation that they may have as the "backing store" for a
list that implements all the correct EMF behaviors.
I've searched the code and have found no use of
these lists within the EMF or XSD plugins. Is there any
documentation for how these can be used? If not, can you provide some
direction? I have a metamodel (i.e., genmodel/ecore model) and generated
code, and my goal is to materialize (lazily) instances of these classes (i.e., a
model) from some backing store. Particularly:
- Are there some logical places to "wrap" existing
list implementations? Modifying generated impls? I can think of
several possibilities, but perhaps there are one or even a few that are more
logical than others.
- What's the mechanism (particularly in
DelegatingEcoreEList) for inserting the logic to populate the list
from the backing store? Are there methods in the DelegatingEcoreEList
that should be overridden? Or, is it more of a listener pattern?
Thanks in advance.
Randall
|