XSLT processor

At a minimum, Medea requires only one third party tool: an XSLT processor. While any processor that adheres to XSLT 2.0 specification can be used, the following tools have been tested:

• Saxon. Excellent open source Java-based processor. http://saxon.sourceforge.net.
• Altova. You can use an XSLT processor built into XML Spy; a free Home Edition is sufficient. It is also a great tool to edit XSLT templates, examine your XMI model file and organize your files. While all existing Medea templates have been developed using XML Spy, this tool is not a requirement. A sample Spy project file is provided in the distribution. http://altova.com.

Modeling tool

Use your favorite modeling tool to design your UML model. There's no requirement as long as the tool can export the model in XMI format. These popular modeling tools have been tested:

• Gentleware Poseidon Community Edition. http://gentleware.com
• MagicDraw UML Community Edition. http://magicdraw.com
• Rational Rose. This veteran commercial tool uses its own format to store UML models. You can use an XMI Add-in to export in XMI: http://www-128.ibm.com/developerworks/rational/library/content/.backup/03July/2500/2834/Rose/rational_rose.html. Rose models can also be imported into MagicDraw using their RConverter utility and then exported into XMI.
• Rational Rose XDE Developer. http://www-306.ibm.com/software/awdtools/developer/rosexde

Build tool

Generated source files can be built and packaged with any IDE or build tool, such as Maven or Ant. Medea offers Ant build file that can be used to build components and applications from the generated code. http://ant.apache.org

Application server

Generated applications and J2EE components can be run in an application container of your choice (you just have to design a template that generates container specific descriptors). Medea offers templates that generate deployment descriptors for two leading application servers.

• JBoss. http://jboss.org
• BEA WebLogic. http://bea.com