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.
Difference between revisions of "Java Workflow Tooling Project"
(→Brainstorming) |
(→Brainstorming) |
||
| Line 36: | Line 36: | ||
* [[JWT Databinding | Databinding in JWT]] | * [[JWT Databinding | Databinding in JWT]] | ||
* [[JWT and STP STPIM | JWT and STP / STP-IM]] Discussion towards a common, consistent vision and tooling of BPM and SOA | * [[JWT and STP STPIM | JWT and STP / STP-IM]] Discussion towards a common, consistent vision and tooling of BPM and SOA | ||
| + | * [[JWT Validation | Design time validation and error checking]] | ||
== Community == | == Community == | ||
Revision as of 10:27, 4 November 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 on JWT
- Mailing list, newsgroup and other sites
- Public Presentations, Press articles and conferences
- Original Project Proposal (end of 2006)
- Draft submission review slides (beginning of 2007)
JWT Installation and Usage Description
- Workflow Editor Installation and Usage Description v0.4.0
- Discussion about User Interface and HMI
- Download the current source code of JWT and try the latest features
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
JWT and AgilPro Extension and Maintenance
- Information on how to extend the Workflow Editor through Plugins
- Information on how parts of the Workflow Editor can be modified/extended
- General information about many recurring development tasks
Brainstorming
- Metamodel discussion
- Writing tests in JWT
- Databinding in JWT
- JWT and STP / STP-IM Discussion towards a common, consistent vision and tooling of BPM and SOA
- Design time validation and error checking
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. You can view them online : All JWT bugs (including resolved ones).
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)
Roadmap
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.
Upcoming releases
- 0.5 JWT WE Stabilization and Openness (improvements of WE and bugfixes, UI extensions) - aiming at the end of October 2008
- 0.6 JWT for Vendors (EMF aspects, completeness and consistency of extensions, first transformations) - aiming at the end of November 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 (June 2009)