Skip to main content
Jump to: navigation, search

Difference between revisions of "Java Workflow Tooling Project"

Line 32: Line 32:
* [[JWT Automatic Build]] - how build is automated (releng)
* [[JWT Automatic Build]] - how build is automated (releng)
== Brainstorming ==
* [[JWT Tests | Writing tests in JWT]]
* [[JWT Databinding | Databinding in JWT]]
* [[JWT_UI| Discussion about User Interface and HMI]]
* [[JWT and STP STPIM | JWT and STP / STP-IM]] Discussion towards a common, consistent vision and tooling of BPM and SOA
* [[JWT Validation | Design time validation and error checking]]
== Community ==
== Community ==

Revision as of 08:29, 20 January 2009


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.

Resources on JWT

JWT Installation and Usage Documentation

JWT and AgilPro developer documentation

JWT Contributor Documentation


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

Back to the top