Jump to: navigation, search

Difference between revisions of "Java Workflow Tooling Project"

(Community)
(Resources concerning JWT)
Line 23: Line 23:
 
* [[JWT Automatic Build]] - how build is automated (releng)
 
* [[JWT Automatic Build]] - how build is automated (releng)
  
== Resources concerning JWT ==
+
== Development Resources ==
=== Development ===
+
* [http://following-flo.blogspot.com/ Blog related to JWT with current news]
+
 
* [[JWT Architecture | Architecture of JWT]]
 
* [[JWT Architecture | Architecture of JWT]]
 
* [[JWT Meetings | Telcos and Meetings of JWT]]
 
* [[JWT Meetings | Telcos and Meetings of JWT]]
* [[JWT Brainstorming | Brainstorming]];;
+
* [[JWT Brainstorming | Brainstorming]]
 
* [[JWT Release Engineering | Release Engineering]]
 
* [[JWT Release Engineering | Release Engineering]]
  

Revision as of 16:50, 1 April 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

Development Resources

Community