| EMF 2.6 M4 EObject.eContainer() [message #505760] |
Mon, 04 January 2010 14:39  |
Eclipse User |
|
|
|
Hi all,
i've read that in EMF 2.6 the inheritance between EObject and
EModelElement was removed. I've investigated the issue discussion at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=255469, where Ed has said,
that instances still realize the reflective operations of EObject, like
eContainer().
However, i haven't tried it, but does this mean, that xyz.eContainer()
is not possible anymore, to get the Container of instance xyz of a
possible class XYZ. If so, a lot of code changes in my program have to
be made... this would be somehow suboptimal for my case.
Cheers
Timothy
|
|
|
| Re: EMF 2.6 M4 EObject.eContainer() [message #505765 is a reply to message #505760] |
Mon, 04 January 2010 10:12  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Hi,
eContainer() on EObject wasn't removed. What was removed was
EModelElement interface inheriting from EObject. So that means
EModelElement.eContainer() is gone. Are you using EModelElement's
directly and assuming they are EObject's?
Timothy Marc wrote:
> Hi all,
>
> i've read that in EMF 2.6 the inheritance between EObject and
> EModelElement was removed. I've investigated the issue discussion at
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=255469, where Ed has said,
> that instances still realize the reflective operations of EObject, like
> eContainer().
>
> However, i haven't tried it, but does this mean, that xyz.eContainer()
> is not possible anymore, to get the Container of instance xyz of a
> possible class XYZ. If so, a lot of code changes in my program have to
> be made... this would be somehow suboptimal for my case.
>
> Cheers
> Timothy
--
Thanks,
Rich Kulp
|
|
|
| Re: EMF 2.6 M4 EObject.eContainer() [message #505862 is a reply to message #505765] |
Tue, 05 January 2010 06:43 |
| Eclipse User |
|
|
|
Guys,
The only model that's affected is Ecore itself. EModelElement still
extends EObject just as it always has, so in terms of binary and API
compatibility, you won't notice the difference. The only difference
you'll notice is EcorePackage.Literals.EMODEL_ELEMENT.getESuperTypes()
is now empty rather than containing EcorePackage.Literals.EOBJECT.
I.e., the explicit inheritance of EModelElement from EObject is removed
from the model.
Rich Kulp wrote:
> Hi,
>
> eContainer() on EObject wasn't removed. What was removed was
> EModelElement interface inheriting from EObject. So that means
> EModelElement.eContainer() is gone. Are you using EModelElement's
> directly and assuming they are EObject's?
>
>
> Timothy Marc wrote:
>> Hi all,
>>
>> i've read that in EMF 2.6 the inheritance between EObject and
>> EModelElement was removed. I've investigated the issue discussion at
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=255469, where Ed has
>> said, that instances still realize the reflective operations of
>> EObject, like eContainer().
>>
>> However, i haven't tried it, but does this mean, that
>> xyz.eContainer() is not possible anymore, to get the Container of
>> instance xyz of a possible class XYZ. If so, a lot of code changes in
>> my program have to be made... this would be somehow suboptimal for my
>> case.
>>
>> Cheers
>> Timothy
>
|
|
|
Powered by
FUDForum. Page generated in 1.08064 seconds
Home