Skip to main content
Jump to: navigation, search


Revision as of 09:15, 6 December 2008 by (Talk | contribs) (Detailed Layout of the CVS)

This site contains information about the dependencies of JWT's components, as well as a description on how to download the latest versions from the Eclipse CVS and the layout of the JWT CVS repositories.

Access the JWT Source Code

The planned and current state of the next release of JWT components can be viewed at Upcoming Release Information.

To download the source code of the various components of JWT, please connect your CVS client (typically Eclipse 3.4's CVS Browsing perspective) with:

  • Host:
  • Repository path: /cvsroot/technology
  • User: anonymous
  • Password: (none)
  • Connection type: pserver

If you have a committer account, please provide your committer data (username and password) and select as connection type extssh instead of pserver.

In this CVS repository, the source code of JWT is under the "org.eclipse.jwt" directory, which you can retrieve by doing a CVS checkout. It is laid out as follow :

  • org.eclipse.jwt/we : Workflow Editor, i.e. design time tools
  • org.eclipse.jwt/wam : Workflow Audit And Monitoring, i.e. runtime time tools and framework
  • org.eclipse.jwt/desktop : Simulator and other standalone BPM tools

For a more detailed layout please refer to Detailed Layout of the CVS.

You can also browse the CVS repository online at .




The easiest way to get an Eclipse environment with all dependencies is to install Eclipse Ganymede JEE Edition and a Java Runtime Environment (JRE) / Java Development Kit (JDK) 5.0 or higher.


Version 0.5.0 of the JWT Workflow Editor (JWT-WE) requires Eclipse (3.4) with the Eclipse Modeling Framework (EMF) and the Graphical Edition Framework (GEF).

If you already have Eclipse installed you can download EMF and GEF from from your "Software updates" menu.


JWT uses Jdom 1.0 from Orbit. To work with it in your workspace, follow the steps described here.

In our case, simply check out in your wrkspace the module described above:

  • host:
  • repository: /cvsroot/tools
  • module: org.eclipse.orbit/org.jdom
  • Tag: v200806100616 (Version)

Get the Code

You need to retrieve the JWT source code by checking it out from CVS, as described above.

If you used an external CVS tool to check out the code, you need to import the source code into Eclipse as projects (in the Java Perspective, using right click > import existing projects).

Run the Plugins from Code

Right click on the jwt-we project and choose Run as > Eclipse application. This will launch JWT-WE with all plugins that are available in the workspace. If Eclipse does not succeed to start or JWT-WE is not active, please ensure that all necessary plug-ins are configured to start with your projects. To do so, click on the arrow in the Run item in toolbar, and choose Run Configuration.... Select/Create a run configuration (Eclipse Application) for JWT-WE and on the Plug-ins tab select all necessary plug-ins (in case you have doubt, select Add Required Plugins). Workflow Editor plugins (e.g. the Documentation Generator plugin) must also be enabled in order to be available at run time. You can now use the Run item in the toolbar to start your new configuration.

Structure of CVS

  • All projects start with jwt.
  • Afterwards the main component is added jwt-we, jwt-transformation or jwt-wam.
  • If an example is visible in a specific area it is named jwt-we-XY-example (for an example using an extension point of the workflow editor).
  • The package structure is org.eclipse.jwt.component and for additional plugins org.eclipse.jwt.component.plugins.nameexample, e.g. org.eclipse.jwt.we.plugins.viewexample.
  • Versioning: It is always x.y.z where x and y are always consistent with the corresponding JWT version and z is reserved for the different versions of the plugin in one release, e.g. 0.4.1 for JWT release 0.4 and first change of this additional plugin.
  • In CVS there will be a main directory for each component jwt-we, jwt-transformation, jwt-wam and in these there is a subdirectory jwt-XY-plugins (e.g. we/jwt-we-plugins/) where all additional plugins can be found.

Detailed Layout of the CVS


Contains everything related to the Workflow Editor

  • jwt-we The Workflow Editor
  • jwt-we-plugins Plugins for the Workflow Editor
    • jwt-we-action-example An Example on how to add Menu/Toolbar Actions to the Workflow Editor
    • jwt-we-action-doc An Action for generating Documentations
    • jwt-we-view-example A Example on how to add Views to the Workflow Editor
    • jwt-we-view-uml A view that displays Processes as UML Activity Diagrams
    • jwt-we-propertyDescriptor-common Commons and generic classes that can be shared between several propertyDescriptors
    • jwt-we-propertyDescriptor-icon propertyDescriptor that replaces TextArea by File System browser for icon
    • jwt-we-propertyDescriptor-jarFile propertyDescriptor that replaces TextArea by File System browser for jarFile
    • jwt-we-propertyDescriptor-applicationMethod propertyDescriptor that replaces TextArea by a combo box when choosing a method in a JavaApplication
    • jwt-we-changeListener-applicationMethod changeListener that automatically sets the parameters of a JavaApplication when able to introspect specified method
  • jwt-view A Program for Creating and Modifying Workflow Editor Views
  • jwt-we-feature JWT-WE Feature (to be published on Update Site)
  • jwt-we-update-site Contents for Update-Site


  • jwt-transformation-base The base plug-in for any transformation. Provides UI
  • jwt-transformation-stub A sample plug-in that is based on jwt-transformation-base
  • jwt-transformation-xpdl JWT to XPDL transformation
  • jwt-transformation-jwt2bpmn(-tests) jwt to bpmn transformation (and tests)


  • jwt-webservices Tools to introspect WSDL
  • jwt-runtime-api A workflow API that is used by monitoring plug-in at runtime to get informations from a workflow engine
  • jwt-monitoring(-test) A plug-in that provides tools to display a workflow state from a workflow engine into JWT (and tests)


JWT releases automated builds. See JWT Automatic Build

See also

Back to the top