Eclipse Community Forums: EMF » Why EModelElement doesn't inherit from EObject?

Help

Home

Home » Modeling » EMF » Why EModelElement doesn't inherit from EObject?

Show: Today's Messages :: Show Polls :: Message Navigator

Why EModelElement doesn't inherit from EObject? [message #890288]

Thu, 21 June 2012 18:47

Marc Mising name

Messages: 193
Registered: July 2009
Location: Valencia, Spain

Senior Member

Hello everybody,

I realized that since at least Indigo release, EModelElement doesn't inherit from EObject element in the Metamodel. Nevertheless, in the generated code EModelElement extends from EObject.

That's a problem, due to for instance XPand transformations doesn't work fine with this change. To solve this problem in XPand, I needed to change eContainer() calls by eContainer. In other words: access directly to the attribute instead of using the function.

Maybe there're other parts of code or transformations where this is a big problem.

Is it correct or is it a bug? If it's a bug, maybe it could be resolved in the Juno final release?

I create a bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=383265

Thanks a lot.
Marc

Report message to a moderator

Re: Why EModelElement doesn't inherit from EObject? [message #890294 is a reply to message #890288]

Thu, 21 June 2012 19:16

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

HI

This change was made in Helios M4 for pragmatic bloat reasons that
coincide with more accurately reflecting the modeling perspective.

In OCL/Acceleo/QVTo you can oclAsType(ecore::EObject) to cast to where
the names are visible.

Regards

Ed Willink

On 21/06/2012 19:47, Marc wrote:
> Hello everybody,
>
> I realized that since at least Indigo release, EModelElement doesn't
> inherit from EObject element in the Metamodel. Nevertheless, in the
> generated code EModelElement extends from EObject.
>
> That's a problem, due to for instance XPand transformations doesn't
> work fine with this change. To solve this problem in XPand, I needed
> to change eContainer() calls by eContainer. In other words: access
> directly to the attribute instead of using the function.
>
> Maybe there're other parts of code or transformations where this is a
> big problem.
>
> Is it correct or is it a bug? If it's a bug, maybe it could be
> resolved in the Juno final release?
>
> I create a bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=383265
>
> Thanks a lot.
> Marc

Report message to a moderator

Re: Why EModelElement doesn't inherit from EObject? [message #890295 is a reply to message #890294]

Thu, 21 June 2012 19:21

Marc Mising name

Messages: 193
Registered: July 2009
Location: Valencia, Spain

Senior Member

So it's not a bug... Nevertheless I don't understand the reason it was done... cause in the generated code it stills extends from EObject...

But thanks for your response Ed.
Marc

Report message to a moderator

Re: Why EModelElement doesn't inherit from EObject? [message #890376 is a reply to message #890295]

Fri, 22 June 2012 07:19

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Marc,

All the generated eInvoke methods for the EModelElement hierarchy, which
includes GMF's Notation model and UML2, would have a large dispatching
switch for all of EObject's operations. But it should never be
necessary or even usual, to eInvoke EObject's operations because all
generated implementation classes implement EObject anyway so you can
always cast to EObject and call its method without eInvoke support.

On 21/06/2012 3:21 PM, Marc wrote:
> So it's not a bug... Nevertheless I don't understand the reason it was
> done... cause in the generated code it stills extends from EObject...
>
> But thanks for your response Ed.
> Marc

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator