Andre Dietisheim [http://community.jboss.org/people/adietisheim] modified the document: "Manually Creating Eclipse EMF Ecore Models" To view the document, visit: http://community.jboss.org/docs/DOC-15697 -------------------------------------------------------------- EMF provides tools for creating an EMF object model from an XML Schema (XSD).  It also provides tools for hand-crafting a model.  This document attempts to describe the process involved in the later. +Note: All Content provided by André Dietisheim.  Thanks André !!+ h1. h1. Forewords There are a few tutorials available on http://www.eclipse.org/modeling/emf/docs/#tutorials eclipse.org, the best one so far's the one provided by http://www.vogella.de/articles/EclipseEMF/article.html Lars Vogella. I'd try to focus on special points here that shall help the guys in the smooks ui to get a jumpstart. If you want to create an ecore model manually, you have different editors at hand that you may use for this matter. The most common one is the *Sample Ecore Model Editor*, but you may also use text based editors like http://wiki.eclipse.org/Emfatic Emfatic or http://www.eclipse.org/Xtext/ Xtext. There are also graphical editors around like the* http://www.eclipse.org/modeling/emft/?project=ecoretools Ecore Diagram Editor or the eUML2 Editor.* h1. Create an EMF Project To get started, create an empty EMF project. http://community.jboss.org/servlet/JiveServlet/showImage/102-15697-7-4890... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15697-7-... You'll get a new project, that's set up to work with the EMF framework. The model definitions, the *ecore* files are put into a *model* folder (not a must but a standard so far). Create a new ecore model file in this folder by selecting the folder and triggering the new ecore model wizard. http://community.jboss.org/servlet/JiveServlet/showImage/102-15697-7-4891... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15697-7-... h1. Create the Package If you want to create an ecore model manually, you have different editors at hand that you may use for this matter. The most common one is the *Sample Ecore Model Editor*, but you may also use text based editors like http://wiki.eclipse.org/Emfatic Emfatic or http://www.eclipse.org/Xtext/ Xtext. There are also graphical editors around like the* http://www.eclipse.org/modeling/emft/?project=ecoretools Ecore Diagram Editor or the eUML2 Editor.* We created the empty ecore model so far, so the next step is to create a package for your model. You set its name, Ns Prefix and Ns URI. The good practice (or at least what most modelers do) is to set them to: * *name*: a simple term (not required to be unique) * *Ns prefix*: ~shoretened 'java package' name (not required to be unique) * *Ns URI*: some real (or bogus) unique URI where the scheme might be found. h4. example I have a plugin/module in cdo called *org.eclipse.emf.cdo.ui.defs* The ecore model for it has the following definitions: *name*: defs *Ns prefix*: cdo.ui.defs *Ns URI*: http://www.eclipse.org/emf/CDO/ui/defs/1.0.0 http://www.eclipse.org/emf/CDO/ui/defs/1.0.0 h1. Model Your Classes You can now add classes to your package. There are usually several ways to get to the desired result, most likely the best way is to get the book or error and trial. A rule of thumb is to have all classes available in your model. This is evident for ecore classes. But if your ecore classes use references to plain java types (that are not part of your ecore model in the strict sense) you'll at least need to declare those java types in the ecore model. In other words, the ecore model needs to know about all types (ecore or plain java) that are part of your model. h4. example1 Let's say that my modeled class CDOEditorDefs has a method execite() that throws an ExecutionException. I could add that method by hand but as a matter of taste I prefer to declare that method in my model. My model does not know anything about this exception so far, so there's no way to get the correct signature generated out of the box . I'll therefore have  to declare this exception in model. I create a DataType ExecutionException. h4. example2 A very common problem is to have modeled (ecore-) classes extend Java Interfaces. For instance this could be java.lang.Comparable The best way to achieve that is to model a class Comparable. Do not model its operation as this is just a mirror of the real java interface in the ecore-world. What differs to real ecore-classes is that you set its instance type name: java.lang.Comparable. You can now add the Comparable class to the super type of each ecore-class you want to. Modeled this way, the generator will not generate an ecore class that's called Comparable but it will include java.lang.Comparable in the interface that your ecore-classes implement. +*Not sure I follow this example and what we're trying to illustrate.  Would example code help?*+ h1. Create a Genmodel This is mostly straight forward. Select the ecore file and create a genmodel for it.  Select your ecore file and start a new *EMF Generator Model* wizard. The wizard will allow you to create a so called Generator Model that holds all settings which are important to the code generation process. http://community.jboss.org/servlet/JiveServlet/showImage/102-15697-7-4847... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15697-7-... There are 2 settings that might be of interest to you: '*All*' (property group when the package is selected): - *Base Package*: the base package all ecore classes get generated to - *Prefix*: Prefix that the factory- and package-class get http://community.jboss.org/servlet/JiveServlet/showImage/102-15697-7-4848... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15697-7-... example (still using the cdo.ui.defs example): *Base Package*:  org.eclipse.emf.cdo.ui *Prefix*: CDOUIDefs Package-class gets CDOUIDefsPackage, Factory gets CDOUIDefsFactory, etc. All classes get generated to the package org.eclipse.emf.cdo.ui Further modifications you might be interested in are the suffixes of the sub-packages (the defaults creates an 'impl' package where it puts all implementation classes). It can be modified by selecting the '*Package Suffixes*' and choosing the properties '*Implementation*' and '*Interfaces*'. The naming of the implementation- and interface-classes may be changed, too. You find those settings if you select the root-node of the tree in the genmodel-editor and choose the '*Model*' property group. You'll find 'Class Name Pattern' and 'Interface Name Pattern' among the available properties. The explanations for the values show up in the statusbar (default is '*{0}impl*' and '*{0}*'). http://community.jboss.org/servlet/JiveServlet/showImage/102-15697-7-4849... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15697-7-... Once you're done defining your generator model, you simply need to generate the implementation classes. Select the package you want to generate, right click and select the implementation you want to create. You may choose among the models, the editor, the tests. http://community.jboss.org/servlet/JiveServlet/showImage/102-15697-7-4850... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15697-7-... h1. Modify the Generated Classes Ecore is built to be modified, the basic usage-pattern is to code and generate hand-in-hand. To tell the generator not to override your modifications you need to set the javadoc-annotation to anything different than '@generated'. Good practice says that you should set it to '@generated NOT'. Good practice also tells you to annotate any manually added method by '@ADDED', but its optional though. There is another handy that allows you to modify and get the generated code. If you want to have your code instead of the generated one, you just annotate accordingly and the generator will preserve your code. If you want the generated code, too, you'd need to create a method that has the original name + a suffix 'Gen' example: /** * * @generated NOT */ public void setName(String name) {     YOUR OWN CODE } /** * * @generated */ public void setNameGen(String name) {     GENERATOR provides the generated code in here } After making your modifications, you simply need to re-generate the ecore classes. (+*How?*+) -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-15697] Create a new document in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&am...]