|Re: km3 -> ecore - bad practice in metamodeling? [message #613642]
||Thu, 20 March 2008 18:53
| Ed Merks
Registered: July 2009
I'm not sure what to say. This issue came up recently on the GMT
newgroup and it's something that KM3 folks need to consider. Something
like annotations to specify things not in KM3 but needed in Ecore would
seem to make sense.
Matti Husu wrote:
> Hi, please tell me what do you think and is there a way to avoid the
> problems below.
> First you specify metamodel with KM3 there has to be Primitive types
> package if classes have attributes (String, Boolean...).
> Then you inject it to a .ecore file. Everything is cool. But if you
> want to make an editor (EMF/GEF or GMF) you need .genmodel.
> This can't be created at least on Eclipse 3.2.1/EMF 2.2.1
> In Eclipse 18.104.22.168 you can but you have to specify nsUri etc for the
> PrimitiveTypes-package and corresponding java classes for Integer etc.
> I think GMF-ecore diagram editor is more handy.
Powered by FUDForum
. Page generated in 0.01641 seconds