Jump to: navigation, search

Difference between revisions of "Java Workflow Tooling Project"

(JWT Contributor Documentation)
(JWT Contributor Documentation)
Line 34: Line 34:
 
* [[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]] somewhat obsolete, rather see [[JWT Ramp-Down-Policy]] and [http://www.eclipse.org/projects/project-plan.php?projectid=soa.jwt project plan].
  
  
 
[[Category:Eclipse Technology Project]]
 
[[Category:Eclipse Technology Project]]

Revision as of 14:04, 22 May 2012

Overview

JWT Website

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.

Get and use Java Workflow Tooling!

JWT Community

  • JWT Resources - Mailing list, newsgroup, original proposal and other sites
  • JWT Press - Public Presentations, conferences, press articles, blogs, forums
  • JWT Integrations - Solutions that integrate and extend JWT

JWT Developer Documentation

JWT Contributor Documentation

Other Development Resources :