|
| Re: eSuperTypes vs. eGenericSuperTypes [message #429153 is a reply to message #429152] |
Fri, 10 April 2009 07:01  |
|
Enrico,
On Aug. 8th, 2007 I asked a similar question here (subject:
eGenericSuperTypes).
Perhaps that thread has some answers for you?
Cheers
/Eike
----
http://thegordian.blogspot.com
Enrico Schnepel schrieb:
> Hello,
>
> I am using COPE to migrate a model which is on the meta level. while saving
> I am getting the strange behavior that a referenced ecore model gets
> modified while it shouldn't. the problem seems to be within emf itself.
>
> COPE uses the reflective interfaces of the meta level (EClass,
> EReference...) to operate on EObjects. when operating on an ecore model an
> EClass EObject has the References eSuperTypes as well as
> eGenericSuperTypes. Because both are not set to IS_DERIVED an other EClass
> is added to them. In my opinion eSuperTypes should be set to isDerived as
> it is documentated in the user doc of EClass.getESuperTypes(). In addition
> both should be set to unique because a double addition of a EClass EObject
> is possible (first with eSuperTypes then with eGenericSuperTypes) which
> results to validation errors when generating a GenModel of it.
>
> Best Regards
>
> Enrico
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.02676 seconds
] 
Search
Help
Register
Login
Home
