Peter Friese is a software engineer with 15+ years hands-on experience in software development, technical writing and public speaking. Peter works as a software engineering consultant at Zühlke Engineering. Having worked on a host of industry projects in diverse domains and being an active committer on a number of open source projects, he has in-depth knowledge in a broad range of technologies. His main areas of expertise are model-driven software development, cross-platform mobile development (iPhone, Android, Windows Phone 7, and mobile web) and Eclipse tooling. Peter blogs at http://www.peterfriese.de and tweets at @peterfriese. Peter is a DZone MVB and is not an employee of DZone and has posted 29 posts at DZone. View Full User Profile

Getting Started With Code Generation With Xpand

03.18.2010
| 17048 views |
  • submit to reddit

Have you heard about model driven software development (MDD / MDSD) and are thinking "what's all this fuzz about models"? "Why should models help me to be more productive," might be another thought you have.

People have been asking how to leverage models on and off on the web and in meetings I attended, so I thought I might share this little tutorial with you. In this tutorial, we will develop a little code generator that helps you to create (HTML) forms from models.

A short Overview

Xpand is a template engine, similar to FreeMarker, Velocity, JET and JSP. However, it features some very unique properties that makes using Xpand very well suited for generating code from models, such as type safety and polymorphic dispatch. If you haven't heard those terms before, fear not! I'll show you how to use Xpand by way of an easy-to-follow example.

The usual process of writing a code generator with Xpand is as follows:

  1. Define the structure of the model you want to process. This is called a metamodel
  2. Define one or more template(s) that teach the code generator how to translate your model into code.

Easy, isn't it?

Using the code generator is even easier:

  1. Create a model
  2. Start the code generator

It is worth mentioning that you can use Xpand to generate code for almost any known programming language. Everything you can express in text can be generated using Xpand. So, while we will be generating HTML and Java code in the following example, you can easily write code templates that generate code for C#, Basic, Lua, SmallTalk, ABAP, or any other programming language. You can also generate manuals and other documentation artifacts from your models using Xpand. I've successfully used Xpand to create DocBook files from models. Those DocBook files have then been converted to PDF files and online help files.

Preparing your IDE

  1. Grab and install a recent copy of Eclipse. At the time of writing, I am using Eclipse 3.6 M6.
  2. Install the latest version of Xpand (Help -> Install New Software ...)
  3. Add the Xpand update site (at the time of this writing, I am using Xpand 1.0 nightly builds from http://download.eclipse.org/modeling/m2t/xpand/updates/nightly/)
  4. Add the MWE update site (http://download.eclipse.org/modeling/emft/mwe/updates/nightly/)
  5. Select MWE and Xpand: Install MWE and Xpand
  6. After the obligatory restart, do yourself the favour and set the platform encoding to UTF-8!

Creating a Generator Project

Xpand code generators are hosted in Eclipse plug-ins, mainly because this makes handling the classpath a lot easier. People have reportedly used Maven to run Xpand code generators, but we won't go down this road today. Let's create a simple generator project:

  1. Open the new project wizard and choose Xpand Project from the list
  2. Choose a meaningful name for your project (e.g. org.xpand.example.gettingstarted
  3. Select Create a sample EMF based Xpand project

After clicking Finish, the wizard will create an sample generator project for you:

Xpand project layout

Before we can start working with this project, we need to perform some clean-up actions:

  1. Open src/metamodel/Checks.chk and delete all its contents
  2. Open src/metamodel/Extensions.chk and delete all its contents
  3. Open src/template/GeneratorExtensions.ext and delete all its contents
  4. Delete src/Model.xmi
  5. Don't forget to save all modified files

Creating the Metamodel

As mentioned before, we need to define the structure of our models before we can actually start writing the code template.
Xpand is capable of understanding a variety of metamodel types. For example, if you have an XML schema file, you can use this as a metamodel and thereby enable Xpand to use XML files which are compliant to your schema as input models. Or, if you already have a bunch of Java files making up your data model, you can use those to drive Xpand code generation. In this tutorial, however, we will be using an Ecore metamodel to define the structure of our models. The project has already been configured to support Ecore metamodels, so all we need to do is open metamodel.ecore and define the structure:

  1. Please open src/metamodel/metamodel.ecore
  2. .

  3. Remove the following elements from the metamodel: Feature, Entity, Datatype, Type, Model. The metamodel should now be empty: Empty metamodel
  4. Select package metamodel (as depicted in the screenshot above) and add a new EClass (context menu -> New Child -> EClass). Use the properties view to change the name of the newly created EClass to Model.
  5. Create a new EClass Form
  6. Select the newly created EClass Form and add the following EAttributes:
    • name, set the EType to EString
    • description, EType = EString
    • title, EType = EString
  7. Select EClass Form and add a new EReference, setting its attributes as follows:
    • name = forms
    • EType = Form
    • Containment = true
    • Upperbound = -1 (meaning: unlimited)
  8. Create a new EClass Field and add the following EAttributes to it:
    • name, EType = EString
    • lable, EType = Estring
  9. Create another EClass TextField, setting its properties as follows:
    • name = TextField
    • ESuper Types = Field
  10. Add one EAttribute text to Textfield:
    • name = text, EType = EString
  11. Add an EClass MultiLineTextField to the metamodel:
    • name = MultiLineTextTield
    • ESuper Types = TextField
  12. Now that we have everythign in place, we finally need to add a reference from Form to Field so we can later add fields to a form. Select EClass Form and add an EReference to it, setting its properties as follows:
    • name = fields
    • EType = Field
    • Containment = true
    • Upperbound = -1 (meaning: unlimited)

Creating a Model

Let's now create a model that follows the structure of the metamodel:

  1. In metamodel.ecore, select EClass Model
  2. Create a model instance by choosing Create Dynamic Instance... from the context menu
  3. Save the model file to src/Model.xmi

The model file editor will now open and you can use the tree editor to input the following model:

  • Add a Form to the model, seeting the following properties:
    • Name: context
    • Description: Send your feedback
    • Title: Contact form
  • Add a TextField to the Form, setting the following properties:
    • Name: name
    • Label: Name
  • Add another TextField to the Form, setting the following properties:
    • Name: email
    • Label: EMail
  • Add a MultiLineTextField to the Form, setting the following properties:
    • Name: message
    • Label: Message

Your model should now look like this:

Contact model

Creating a Code Generator

As mentioned before, we will create a code generator for simple forms. Nothing too fancy, but enough to give you an idea of how to create generator templates.

The result will look like this:

Contact Form

Open src/template/Template.xpt and replace its contents with the following text:

«IMPORT metamodel»
«DEFINE main FOR Model»
«EXPAND form FOREACH forms»
«ENDDEFINE»

On the first line, we import the metamodel so that the generator (and the editor as well) knows about the structure of our model. On line 2 - 4 we define a code template named main, making sure it is bound to model elements of type Model. The template doesn't do much, except to call another template (which we will define in a minute) named form with the collection of Forms, contained in the reference forms of the current form.

Add the following lines to the template file, defining the template for the HTML file:

«DEFINE form FOR Form»
«FILE name + ".html"»
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <title>«this.title»</title>
  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  <link rel="stylesheet" type="text/css" href="../static/style.css" />
</head>

In the first line, we start the template by specifying its name (form) and the type it is bound to (Form). On the next line, we use the FILE statement to specify the file the output is going to be written to. The name of the file is derived by concatenating the attribute name of the current Form and the string literal ".html".

Continue the template by appending the following text:

<body>
  <div id="page-wrap">
    <h1>«this.title»</h1><br /><br />
    <p>«this.description»</p>
    <div id="form-area">

Obviously, this piece of template code will create part of the body of the HTML page. Again, we will access attributes of the current Form (as read from the model) and insert their values into the template (in this case, the title and the description). By the way, you can omit the this. prefix in front of the variable names.

The template goes on with the following text:

      <form method="post" action="form.php">
        «EXPAND field FOREACH this.fields»
        <input type="submit" name="submit" value="Submit" class="submit-button" />
      </form>
      <div style="clear: both;"></div>
    </div>
  </div>
</body>
</html>
«ENDFILE»
«ENDDEFINE»

The EXPAND statement will invoke yet another subtemplate with the name field. This sub template will be called for each element in the fields attribute (reference) of the current Form.

You might recall that we we defined three different kinds of >Fields in the metamodel:

  1. Field (which is the super class for the other two field types
  2. TextField
  3. MultiLineTextField

As their names imply, a TextField will be a single line text entry field, whereas MultiLineTextField will be a multiline text input field. We somehow need to be able to render different HTMNL code for each of these different text field types.

As mentioned in the introduction, Xpand is not only type safe, but also supports polymorphic dispatch. This basically means we will create three templates (one for each of the different field types) with the same name. When evaluating the code template, the Xpand generator will dispatch to the appropriate template by matching the most concrete type of the current model element.

Add the following code to the template file:

«DEFINE field FOR Field»
«ERROR "should not happen"»
«ENDDEFINE»
«DEFINE field FOR TextField»
        <label for="«this.name»">«this.label»:</label>
        <input type="text" name="«this.name»" id="«this.name»" />
«ENDDEFINE»
«DEFINE field FOR MultiLineTextField»
        <label for="«this.name»">«this.label»:</label>
        <textarea name="«this.name»" id="«this.name»" rows="20" cols="20"></textarea>
«ENDDEFINE»

As you can see, all three templates have the same name. Only the type they are bound to differs. This is enough to let Xpand know which template to choose according to the type of the current model element. Let's suppose Xpand is iterating the model and the current model element is a TextField. Although Field is a direct super type of TextField, Xpand will not invoke the first template («DEFINE field FOR Field»), but the second template («DEFINE field FOR TextField»), as this is the most concrete match for the type of the model element.

Running the Code Generator

If you have followed the above steps, running the code generator is a piece of cake:

Open the context menu on src/workflow/workflow.mwe and select Run As -> MWE Workflow

This will start the code generator. You will see some log messages in the console view. If all went well, the output in the console reads something like this:

...
1503 INFO  Generator          - Written 1 files to outlet [default](src-gen)
1503 INFO  WorkflowRunner     - workflow completed in 650ms!

The result of the code generation can be found in src-gen/contact.html. As this file has some dependencies to CSS/image files, please download the files from the static folder (here) and place them in your project before opening contact.html in your browser.

Where to go from here

If you want to learn more about Xpand, be sure to attend my talk Use models and let the computer do the grunt work with Xpand at EclipseCon 2010. I'll show some more advanced topics in this talk (such as generator cartridges, using Xtend to augment your models, partitioning your code templates, using other metamodels to define your models).

Xpand comes with an extensive documentation (just go to Help -> Help Contents -> Xpand Documentation in Eclipse). You can also get help on Xpand in the Eclipse Community Forums

Should you need help, itemis (the company I work with) offers training and consulting for Xpand and a host of other modeling related technologies.

No doubt you have heard about Xtext. Xpand and Xtext go together great: you can use Xtext to define the structure of your models and create great-looking text editors to edit your models. Then, use Xpand to create code generators that take your textual models and turn them into running software. Actually, Xtext comes with a wizard that you to create a code generator project for your DSL.

Downloads

The code for this tutorial can be found in my SVN repository on Google Code.

From http://www.peterfriese.de

Published at DZone with permission of Peter Friese, author and DZone MVB.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Tags:

Comments

Gabriel Forro replied on Mon, 2010/03/22 - 3:50am

Nice article. Simple and descriptive.

Probably there is a typo in step 6. of "Creating the Metamodel" chapter: forms should be added to the Model metamodel type.

Ronald Kinion replied on Mon, 2010/03/22 - 9:05pm

For some reason I do not get the Editor described under the "Creating a Model" I get a plain xml properties editor and nothing like the tree shown in the example image at the bottom of the section. I eventually had to look at the source code to get the proper xml that should fit in there.

Ronald Kinion replied on Tue, 2010/03/23 - 2:15pm

Ok, I went around trying to install various plug-ins and I don't know how I did it, but I somehow managed to get the correct editor to apply to the xsi file to match the screenshot. (Sample Reflective Ecore Model Editor. I also went to project->properties->Xtend/Xpand and made sure XSD Metamodels and EMF Metamodels were activated.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.