Skip to main content

Notice: This Wiki is now read only and edits are no longer 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"

(Community)
(Overview)
Line 1: Line 1:
 
== Overview ==
 
== 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.
+
 
 +
This page is outdated. Please refer to the [[Java_Workflow_Tooling_Project| Java Workflow Tooling Project wiki site]]
  
 
== Architecture ==
 
== Architecture ==

Revision as of 11:29, 25 September 2008

Overview

This page is outdated. Please refer to the Java Workflow Tooling Project wiki site

Architecture

The following describes a possible view of the architecture with a model-driven development view:

JWT Architecture v1.png

Resources on JWT

JWT Installation and Usage Description

JWT and AgilPro documentation

JWT and AgilPro Extension and Maintenance

Brainstorming

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

See also

Back to the top