Jump to: navigation, search

Difference between revisions of "Java Workflow Tooling Project"

(JWT Contributor Documentation)
(JWT and AgilPro developer documentation)
Line 12: Line 12:
 
* [[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 and AgilPro 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 :
* JWT Architecture: [http://wiki.eclipse.org/images/7/78/JWT_Architecture_v1.png JWT architecture overview]
+
* [http://wiki.eclipse.org/images/7/78/JWT_Architecture_v1.png JWT Architecture] - JWT architecture overview
 
* [[JWT Metamodel]]- JWT model core design, extensions and governance
 
* [[JWT Metamodel]]- JWT model core design, extensions and governance
* JWT WE architecture: [http://pvs.informatik.uni-augsburg.de/wiki/index.php/AgilPro_documentation Documentation about JWT/AgilPro, how the code is structured, how it is checked out from the SVN / CVS, how it is used...]
+
* [http://pvs.informatik.uni-augsburg.de/wiki/index.php/AgilPro_documentation JWT WE architecture] - Documentation about an old version and integration of JWT named AgilPro
* JWT WAM architecture: [http://wiki.eclipse.org/images/8/8e/JWT_WAM_and_AgilPro_IFW.pdf Alignment of JWT WAM and AgilPro IFW/AFW]
+
* [http://wiki.eclipse.org/images/8/8e/JWT_WAM_and_AgilPro_IFW.pdf JWT WAM architecture]  Alignment of JWT WAM and AgilPro IFW/AFW
 
* [[JWT Transformations]] - Compatibility tools with other standards and languages
 
* [[JWT Transformations]] - Compatibility tools with other standards and languages
 
* [[JWT Monitoring]] - Monitoring of Workflow Engines in JWT
 
* [[JWT Monitoring]] - Monitoring of Workflow Engines in JWT

Revision as of 07:37, 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

Roadmap & Release engineering

JWT Ramp-Down-Policy

JWT Releases and Roadmaps

Available releases

  • JWT WE available on CVS - as of 2007/10/16
  • JWT WE 0.4 : released on 2008/03/03. Release review slides : Release Review slides , approved on 2008/02/27.
  • JWT WE 0.5 "Stabilization and Openness" (improvements of WE and bugfixes, UI extensions) : released on 2008/10/29. Release review slides : File:JWT Release Review 0 5 v4.pdf , approved on 2008/10/29.

Upcoming releases

  • 0.6 JWT for Vendors (EMF aspects, completeness and consistency of extensions, first transformations) - aiming at the end 2008
  • 0.7 JWT for SOA (more transformations, runtime APIs in WAM, service search UI, service applications model) - Start of 2009
  • 1.0 JWT for Users (With comprehensive testing and documentation,and one or more advised target workflow engine working as well) - aiming at Galileo timeline (may 2009)

JWT Releng