Guys,
Wasn't this the case where EMF uses one arbitrary, but concrete,
subclass of the abstract target type to create a proxy instance?
Cheers
/Eike
----
http://thegordian.blogspot.com
Ed Merks schrieb:
Martin,
We can't create a proxy for an abstract class. There must be an
xsi:type (or a QName in the list) if the type of the feature is abstract.
Martin Taal wrote:
Hi Ed,
A question, how does EMF create a proxy object when the ereference
points to an abstract eclass? I mean the proxyurl or xml does not
necessarily contain the actual concrete eclass of the referenced
instance (or does it...).