Jump to: navigation, search

Difference between revisions of "Java Workflow Tooling Project"

(JWT Installation and Usage Documentation)
Line 14: Line 14:
  
 
== JWT Installation and Usage Documentation ==
 
== JWT Installation and Usage Documentation ==
* latest release : [http://wiki.eclipse.org/images/3/3b/JWTUsageTutorial_v0_4.pdf Workflow Editor Installation and Usage Tutorial v0.4.0]
+
* [[JWT_Downloads|Download and install JWT]]
** (obsolete) AgilPro 1.3.0 tutorial : [http://wiki.eclipse.org/Image:AgilProLiMo_JWT_WE_Installation_Usage_Tutorial_1.3.0.pdf Installation and usage of the AgilPro 1.3.0 workflow editor]
+
* latest release documentation : [http://wiki.eclipse.org/images/3/3b/JWTUsageTutorial_v0_4.pdf Workflow Editor Installation and Usage Tutorial v0.4.0]
* latest developments : [[JWT_CVS| Download the current source code of JWT]] and try the latest features
+
* (obsolete documentation) AgilPro 1.3.0 tutorial : [http://wiki.eclipse.org/Image:AgilProLiMo_JWT_WE_Installation_Usage_Tutorial_1.3.0.pdf Installation and usage of the AgilPro 1.3.0 workflow editor]
 +
* [[JWT_CVS| Download the current source code of JWT]] and try the latest features
  
 
== JWT and AgilPro developer documentation ==
 
== JWT and AgilPro developer documentation ==

Revision as of 09:08, 7 January 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.

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 Documentation

JWT and AgilPro developer documentation

JWT Contributor Documentation

Brainstorming

Community

  • Mailing list (jwt-dev@eclipse.org): Subscribe and see archives at https://dev.eclipse.org/mailman/listinfo/jwt-dev
  • Newsgroup : eclipse.technology.jwt on the eclipse.org news server, whose archives are available at http://dev.eclipse.org/newslists/news.eclipse.technology.jwt/maillist.html
  • Bugzilla : All JWT bugs (including resolved ones)
    • If you are interested in receiving bug messages in your bugzilla account : there are three dummy mail-addresses for the components of JWT, named jwt.we-inbox@eclipse.org, jwt.desktop-inbox@eclipse.org, jwt.wam-inbox@eclipse.org , so copy this comma-separated list in Prefs / Email settings to your user watch list in Bugzilla.

Meetings

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