Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

MWE New Noteworthy

Revision as of 09:14, 23 June 2009 by (Talk | contribs) (General: wording)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


The version 0.7.0 of the Modeling Workflow Engine component (MWE in short) of the EMFT project is the first official Eclipse release of it. The Modeling Workflow Engine allows to orchestrate all kinds of workflows that are needed for model transformations, e.g. code generation or model-to-model transformations.

MWE (back then known just as Workflow Engine) has previously been a part of openArchitectureWare since years and it has been used successfully in many big projects.

Main Features

Creating workflows

MWE uses an XML-based language to create, configure, and then run workflows. A simple, strongly shortened workflow could look like this:


Workflows are built out of workflow components. These components can be either the ones that are provided already by other modeling components (e.g. Xpand or Xtext) or new ones can be constructed by inheriting and implementing a certain base class.

All Workflow components provide certain properties. These properties can be set via bean-like setters, which in term can be accessed and set from the workflow file itself.

IDE support

The Modeling Workflow engine comes with an editor that provides syntax highlighting for workflows (see screenshot above).

Running Workflows

Workflows most of the time are executed directly from within the IDE. However, it is also possible to run workflows from the commandline or from within another program. Additionally, an Ant task is provided that allows to integrate MWE into Ant scripts.

Back to the top