|Re: [ATL] KM3-Ecore primitive types mapping [message #62124 is a reply to message #62053]
||Fri, 21 September 2007 19:23
| Frédéric Jouault
Registered: July 2009
> The problem is that KM3-generated Ecore files use a "PrimitiveTypes"
> package with types as String, Boolean, etc. instead of using the
> standard built-in Ecore types like EString e EBoolean: that prevents me
> from using Ecore API to create conforming model as it seems not to know
> how to convert from a Java String to a the KM3 String "primitive type",
> but only to Ecore standard EString.
Actually, I believe the problem is that the EDataTypes created by the
KM3 to Ecore transformation do not have an appropriate value for
> Is there a way to generate "standard" .ecore files from KM3?
We do not like to have our metamodels point to Ecore elements (e.g.,
EString, EInteger). The reason is that, in such a case, the metamodel
somehow becomes an extension of the metametamodel.
That being said, you can always modify the KM3 to Ecore transformation
to use EString, EInteger, etc. Or, you may also change this
transformation to initialize the instanceClassName attributes of the
generated EDataTypes. The transformation is available in the ATL
Future versions of KM3 will come with this mechanism built-in ;-).
Powered by FUDForum
. Page generated in 0.01375 seconds