Jump to: navigation, search

Difference between revisions of "Java Workflow Tooling Project"

(Roadmap & Release engineering)
(JWT developer documentation)
Line 8: Line 8:
 
* [[JWT_CVS| Download the current source code of JWT]] and try the latest features
 
* [[JWT_CVS| Download the current source code of JWT]] and try the latest features
  
== JWT developer documentation ==
+
== JWT Developer Documentation ==
 
* [[JWT_Extensions|Extending JWT]] - How to extend JWT through Plugins and available extension points. To go further :
 
* [[JWT_Extensions|Extending JWT]] - How to extend JWT through Plugins and available extension points. To go further :
 
* [http://wiki.eclipse.org/images/7/78/JWT_Architecture_v1.png JWT Architecture] - JWT architecture overview
 
* [http://wiki.eclipse.org/images/7/78/JWT_Architecture_v1.png JWT Architecture] - JWT architecture overview

Revision as of 07:56, 20 January 2009

Overview

JWT aims to provide both build-time and runtime generic tools for workflow engines. It is composed of several tools: the WE (Workflow Editor) to model the workflows and WAM (Workflow engine Administration and Monitoring tool) for monitoring and deployment. JWT also aims to provide generic APIs for defining and administrating business processes, in order to achieve said genericity. Addtionally, we will provide the user with several transformations: a user can start modeling his/her processes in BPMN, transform those to JWT, enrich them with technical details and then deploy them on a process engine. Therefore, we develop transformations from BPMN to JWT, from JWT to BPMN, from JWT to XPDL, from JWT to STP-IM, etc.

JWT Installation and Usage Documentation

JWT Developer Documentation

JWT Contributor Documentation

Resources concerning JWT