Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Java Workflow Toolbox Project"

(JWT Installation and Usage Description)
(JWT and AgilPro)
Line 19: Line 19:
 
* [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 Documentation about JWT/AgilPro, how the code is structured, how it is checked out from the SVN / CVS, how it is used...]
 
* [http://wiki.eclipse.org/Image:AgilProLiMo_JWT_WE_Installation_Usage_Tutorial_1.3.0.pdf Installation and usage of the workflow editor]
 
* [http://wiki.eclipse.org/Image:AgilProLiMo_JWT_WE_Installation_Usage_Tutorial_1.3.0.pdf Installation and usage of the workflow editor]
 +
* [[JWT Transformations | Compatibility tools with other standards and languages (ie transformations)]]
  
 
== Community ==
 
== Community ==

Revision as of 10:48, 5 March 2008

Overview

JWT aims to provide both build-time and runtime generic tools for workflow engines. It will initially be composed of two tools, WE (Workflow Editor) and WAM (Workflow engine Administration and Monitoring tool). JWT also aims to provide generic APIs for defining and administrating business processes, in order to achieve said genericity.


Resources


JWT Installation and Usage Description

JWT and AgilPro

Community


Meetings

IP Log

Roadmap

  • JWT WE available on CVS - as of 2007/10/16
  • JWT WE 0.4 release packaging - aiming at the end of February 2008 (Release Review slides)
  • JWT WAM available on CVS - in the middle of 2008
  • JWT for SOA (SCA, BPMN and XPDL/Bonita integration) - aiming at August 2008

Back to the top