|
| Re: why some Ecore EReferences are now changeable=false ? [message #430571 is a reply to message #430565] |
Wed, 27 May 2009 15:14  |
 Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Didier,
Comments below.
Didier Vojtisek wrote:
> Hi,
> I've recently reopen some old transformations that was transforming
> ecore models.
What kinds of transformations?
> They where working fine with previous version of EMF, but doesn't work
> with EMF 2.4.
> After an analysis, it appears that some EReferences in Ecore.ecore are
> not changeable anymore so the transformation fails to set these values...
> for example, I cannot directly set the ePackage of an EClassifier, in
> order to do that I have to reverse the logic and change my
> transformation in order to add the EClassifier in EPackage.eClassifiers
If I look in the history of EClassifierImpl, there's never been an
setEPackage method. I think there was a bug in the generator that
didn't properly preserve the Ecore.ecore's EClassifier.ePackage
feature's changeable=false setting (it's always been this way in the CVS
history) so the EcorePackage.eINSTANCE's setting was inconsistent.
>
> This is weird since these EReference are opposite and are finally
> modified ...
>
> I really wonder why this have been changed in Ecore metamodel ?
A fix to a generator bug. Sorry...
>
> best regard
> Didier
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03090 seconds
] 
Search
Help
Register
Login
Home
