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.
Difference between revisions of "Java Workflow Toolbox Project"
(→Resources) |
(→Meetings) |
||
| Line 43: | Line 43: | ||
* [[JWT Checkpoint Telco 20070516|JWT Checkpoint Telco (16 May 2007)]] | * [[JWT Checkpoint Telco 20070516|JWT Checkpoint Telco (16 May 2007)]] | ||
* [[JWT Checkpoint Telco 20071031|JWT Checkpoint Telco (31 October 2007)]] | * [[JWT Checkpoint Telco 20071031|JWT Checkpoint Telco (31 October 2007)]] | ||
| + | * [[JWT Checkpoint Telco 20080704|JWT Checkpoint Telco (4 July 2008)]] | ||
== IP Log == | == IP Log == | ||
Revision as of 07:39, 4 July 2008
Contents
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:
Resources
- Project Proposal
- Additional resources
- Draft submission review slides
- Public Presentations, Press articles and conferences
JWT Installation and Usage Description
- Workflow Editor Installation and Usage Description v0.4.0
- Discussion about User Interface and HMI
- Download the source code of JWT
JWT and AgilPro documentation
- Alignment of JWT WAM and AgilPro IFW/AFW
- Documentation about JWT/AgilPro, how the code is structured, how it is checked out from the SVN / CVS, how it is used...
- Installation and usage of the workflow editor
- Compatibility tools with other standards and languages (ie transformations)
- Monitoring of Workflow Engines in JWT
Brainstorming
Community
- Newsgroup : eclipse.technology.jwt on the eclipse.org news server, whose archives are available here : http://dev.eclipse.org/newslists/news.eclipse.technology.jwt/maillist.html
- Old mailing list : https://forge.openwide.fr/mail/?group_id=61
- New mailing list (jwt-dev@eclipse.org): Subscribe at https://dev.eclipse.org/mailman/listinfo/jwt-dev.
- 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. If you are interested in receiving bug messages, please copy this comma-separated list in Prefs / Email settings to your user watch list in Bugzilla.
Meetings
- JWT Kickoff Meeting (5 Feb. 2007)
- JWT Checkpoint Telco (3 May 2007)
- JWT Checkpoint Telco (16 May 2007)
- JWT Checkpoint Telco (31 October 2007)
- JWT Checkpoint Telco (4 July 2008)
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