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 "JWT Galileo Summary"
(→Paragraph on developerWorks article) |
m (→Paragraph on developerWorks article) |
||
| Line 6: | Line 6: | ||
=== Paragraph on developerWorks article === | === Paragraph on developerWorks article === | ||
| − | There is never a single kind of workflow | + | There is never a single kind of workflow or process developer. Everybody sees a workflow with different eyes: the business analyst more abstract with only the names of the actions and the IT developer quite concrete with service interfaces and operations. Hence, the project goal of the Java Workflow Tooling (JWT) framework is to allow users not only to model processes in one view, but to refine them, import them from other representations and export them afterwards in order to execute them on existing process and workflow engines. |
Thereby, JWT offers users an adaptable and extensible set of tools in Eclipse for code generation (e.g. XPDL-code, but also HTML documentation), deployment, execution and monitoring of business processes. Fitted with a flexible mechanism that allows to customize the underlying EMF core model and with support for all kind of views, vendors can build tools on top of JWT suited for their domain. | Thereby, JWT offers users an adaptable and extensible set of tools in Eclipse for code generation (e.g. XPDL-code, but also HTML documentation), deployment, execution and monitoring of business processes. Fitted with a flexible mechanism that allows to customize the underlying EMF core model and with support for all kind of views, vendors can build tools on top of JWT suited for their domain. | ||
Revision as of 08:41, 15 June 2009
JWT Galileo (version 0.6.0) Short Summary
This summary is also used for an article on IBM developerWorks about the new Galileo release. On this page we summarize the paragraph about JWT in this article.
Paragraph on developerWorks article
There is never a single kind of workflow or process developer. Everybody sees a workflow with different eyes: the business analyst more abstract with only the names of the actions and the IT developer quite concrete with service interfaces and operations. Hence, the project goal of the Java Workflow Tooling (JWT) framework is to allow users not only to model processes in one view, but to refine them, import them from other representations and export them afterwards in order to execute them on existing process and workflow engines.
Thereby, JWT offers users an adaptable and extensible set of tools in Eclipse for code generation (e.g. XPDL-code, but also HTML documentation), deployment, execution and monitoring of business processes. Fitted with a flexible mechanism that allows to customize the underlying EMF core model and with support for all kind of views, vendors can build tools on top of JWT suited for their domain.