[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
[news.eclipse.tools.emf] Suppress EMF Types=true, Root Extends Class="", Root Extends Interface=""
|
Hello,
I am looking at EMF (2.0.0) to generate code, and would like "to use
standard Java, rather than EMF, collection and object types for features and
operations". I have found a (new?) boolean option "Suppress EMF Types" in
the genmodel properties which is set to true, and a "Root Extends Class" and
a "Root Extends Interface" both of which I set to empty strings, and
experimented with it, but...have some issues, like:
*) The Impl classes still uses protected EList xyz. I want that to be List,
too, just like on the interface now. (In fact, ideally I would actually like
Many=True attributes it to be Collection or Set, not List, anyway, but
setting Ordered to false doesn't seem to do that?)
*) The Impl classes have got tons of compile time errors, because I set
"Root Extends Class" to empty, I want to inherit from java.lang.Object, not
from org.eclipse.emf.ecore.impl.EObjectImpl, I don't want notification nor
other EObject features, how to disable that?
If that's not possible / not the intended usage, I guess I'd have to define
my own templates, correct? Well, how? ;) I am aware of
http://www.eclipse.org/articles/Article-JET/jet_tutorial1.html and
http://www.eclipse.org/articles/Article-JET2/jet_tutorial2.html, but haven't
actually tried it yet, is that still about right for 2.0.0? Noticed a New
Java Emitter Template/Convert Projects to JET Projects, that replaces Add
JET Nature, else also the same? What are the genmodel properties "Dynamic
Templates", "Template Directory" etc. used for?
Thank you very much,
Michael