|
Re: xsd.ecore is not based on ecore.ecore [message #76177 is a reply to message #76158] |
Fri, 07 November 2008 15:47 |
Ed Merks Messages: 33142 Registered: July 2009 |
Senior Member |
|
|
Joachim,
Comments below.
Joachim Back wrote:
> Hi XSD developers,
>
> I relate to org.eclipse.xsd_2.4.1.v200808251517.jar.
>
> I found out, that xsd.ecore is unlike e.g. uml.ecore not based on
> ecore.ecore.
Not sure what you mean by that. It certainly doesn't extend the Ecore
metamodel. UML shouldn't have either, but they ignored me. :-P
>
> Despite of the fact, that e.g. XSDConcreteComponent extends EObject,
> it is not possible to access the functionality of ecore::EObject via
> xsd::XSDConcreteComponent. Hence I cannot access e.g. the eResource()
> method within an oAW xTend.
Why do you think it's not possible? It's definitely possible.
>
> Can someone please explain to me, why the modeling of
> XSDConcreteComponent in xsd.ecore is different from the JAVA code?
There's a difference between explicitly extending EObject (having the
EClass have EObject in the eSuperTypes) and implicitly extending it (all
modeled objects implement EObject and InternalEObject)...
>
> Have a look to uml.ecore to see how it can work. E.g. for
> uml::Package, I can access all methods of ecore::EObject in an oAW xTend.
I think this is more a question for xtend. They should assume that
EObject's methods are available even if the model doesn't have explicit
inheritance.
>
> Regards,
> Joachim Back
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Re: xsd.ecore is not based on ecore.ecore [message #603416 is a reply to message #76158] |
Fri, 07 November 2008 15:47 |
Ed Merks Messages: 33142 Registered: July 2009 |
Senior Member |
|
|
Joachim,
Comments below.
Joachim Back wrote:
> Hi XSD developers,
>
> I relate to org.eclipse.xsd_2.4.1.v200808251517.jar.
>
> I found out, that xsd.ecore is unlike e.g. uml.ecore not based on
> ecore.ecore.
Not sure what you mean by that. It certainly doesn't extend the Ecore
metamodel. UML shouldn't have either, but they ignored me. :-P
>
> Despite of the fact, that e.g. XSDConcreteComponent extends EObject,
> it is not possible to access the functionality of ecore::EObject via
> xsd::XSDConcreteComponent. Hence I cannot access e.g. the eResource()
> method within an oAW xTend.
Why do you think it's not possible? It's definitely possible.
>
> Can someone please explain to me, why the modeling of
> XSDConcreteComponent in xsd.ecore is different from the JAVA code?
There's a difference between explicitly extending EObject (having the
EClass have EObject in the eSuperTypes) and implicitly extending it (all
modeled objects implement EObject and InternalEObject)...
>
> Have a look to uml.ecore to see how it can work. E.g. for
> uml::Package, I can access all methods of ecore::EObject in an oAW xTend.
I think this is more a question for xtend. They should assume that
EObject's methods are available even if the model doesn't have explicit
inheritance.
>
> Regards,
> Joachim Back
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03271 seconds