| Element extends EModelElement? For what purpose? [message #478550] |
Thu, 25 June 2009 08:25  |
Eclipse User |
|
|
|
Hey all,
after investigating the UML.ecore, i just wondering that UML::Element
extends ECore::EModelElement... i've expected a <<instance of>>
relationsship between UML::Element and Ecore::EClass...
For what purpose was this generalization declared?
Thanks
Timothy
|
|
|
| Re: Element extends EModelElement? For what purpose? [message #478552 is a reply to message #478550] |
Thu, 25 June 2009 10:16  |
| Eclipse User |
|
|
|
Timothy,
This generalization was introduced (way back in 2002) to reuse the
annotation mechanism from EMF. There are pros and cons to this(many of
which have been pointed out over the years), but it is what it is. ;)
Kenn
Timothy Marc wrote:
> Hey all,
>
> after investigating the UML.ecore, i just wondering that UML::Element
> extends ECore::EModelElement... i've expected a <<instance of>>
> relationsship between UML::Element and Ecore::EClass...
>
> For what purpose was this generalization declared?
>
> Thanks
> Timothy
|
|
|
| Re: Element extends EModelElement? For what purpose? [message #627730 is a reply to message #478550] |
Thu, 25 June 2009 10:16 |
| Eclipse User |
|
|
|
Timothy,
This generalization was introduced (way back in 2002) to reuse the
annotation mechanism from EMF. There are pros and cons to this(many of
which have been pointed out over the years), but it is what it is. ;)
Kenn
Timothy Marc wrote:
> Hey all,
>
> after investigating the UML.ecore, i just wondering that UML::Element
> extends ECore::EModelElement... i've expected a <<instance of>>
> relationsship between UML::Element and Ecore::EClass...
>
> For what purpose was this generalization declared?
>
> Thanks
> Timothy
|
|
|
Powered by
FUDForum. Page generated in 0.32925 seconds
Home