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 Tooling Project"
(→JWT and AgilPro developer documentation) |
(→JWT and AgilPro developer documentation) |
||
| Line 20: | Line 20: | ||
== JWT and AgilPro developer documentation == | == JWT and AgilPro developer documentation == | ||
* [[JWT_Extensions]] - Extending the Workflow Editor through Plugins and extension points. To go further : | * [[JWT_Extensions]] - Extending the Workflow Editor through Plugins and extension points. To go further : | ||
| − | * JWT WE | + | * JWT WE architecture: [http://pvs.informatik.uni-augsburg.de/wiki/index.php/AgilPro_documentation Documentation about JWT/AgilPro, how the code is structured, how it is checked out from the SVN / CVS, how it is used...] |
| − | + | * JWT WAM architecture: [http://wiki.eclipse.org/images/8/8e/JWT_WAM_and_AgilPro_IFW.pdf Alignment of JWT WAM and AgilPro IFW/AFW] | |
| − | * JWT WAM | + | |
| − | + | ||
* [[JWT Transformations]] - Compatibility tools with other standards and languages | * [[JWT Transformations]] - Compatibility tools with other standards and languages | ||
* [[JWT Aspects]] - Enriching JWT's metamodel with custom business or technical information | * [[JWT Aspects]] - Enriching JWT's metamodel with custom business or technical information | ||
Revision as of 14:05, 5 January 2009
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
- JWT Website
- JWT Resources - Mailing list, newsgroup, original proposal and other sites
- Public Presentations, Press articles and conferences
JWT Installation and Usage Documentation
- latest release : Workflow Editor Installation and Usage Tutorial v0.4.0
- (obsolete) AgilPro 1.3.0 tutorial : Installation and usage of the AgilPro 1.3.0 workflow editor
- latest developments : Download the current source code of JWT and try the latest features
JWT and AgilPro developer documentation
- JWT_Extensions - Extending the Workflow Editor through Plugins and extension points. To go further :
- JWT WE architecture: Documentation about JWT/AgilPro, how the code is structured, how it is checked out from the SVN / CVS, how it is used...
- JWT WAM architecture: Alignment of JWT WAM and AgilPro IFW/AFW
- JWT Transformations - Compatibility tools with other standards and languages
- JWT Aspects - Enriching JWT's metamodel with custom business or technical information
- JWT Monitoring - Monitoring of Workflow Engines in JWT
JWT contributor documentation
- JWT_DeveloperFAQ - General information about many recurring development tasks. Also :
- JWT Modification Guidelines - Information on how parts of the Workflow Editor can be modified / extended
- JWT Ramp-Down-Policy - all necessary informations to integrate JWT into Eclipse Releases
- JWT Automatic Build - how build is automated
Brainstorming
- Metamodel discussion
- Writing tests in JWT
- Databinding in JWT
- Discussion about User Interface and HMI
- JWT and STP / STP-IM Discussion towards a common, consistent vision and tooling of BPM and SOA
- Design time validation and error checking
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
- 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)
- JWT Checkpoint Telco (4 November 2008)
Roadmap & Release engineering
JWT Ramp-Down-Policy
- JWT Ramp-Down-Policy contains all necessary informations to integrate JWT into Eclipse Releases
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
- JWT Automatic Build explains how build is automated.