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 "Why use JWT"
m (→Is JWT just another graphical editor?) |
(→Questions & Answers) |
||
| Line 1: | Line 1: | ||
== Questions & Answers == | == Questions & Answers == | ||
| − | === Is JWT just another graphical editor? === | + | === Is JWT just another graphical business process editor? === |
| + | |||
| + | No! Java Workflow Tooling aims to support the whole BPM lifecycle reaching from the designing of workflows to their execution and monitoring. | ||
| + | |||
| + | === So what is the goal of this project? === | ||
| + | |||
| + | The goal of the JWT project is to offer vendors an open and flexible framework that can be adjusted to their needs. JWT is designed to be easily extensible and can therefore be made to work together with a variety of different existing tools and standards. | ||
=== Why should I use JWT instead of tool XYZ? === | === Why should I use JWT instead of tool XYZ? === | ||
| − | + | JWT does not need to replace an existing tooling but can instead be considered to be a framework that brings together different programs and standards and may be used to bridge incompatibilities and add additional functionality. | |
| + | |||
| + | === Can I use JWT with my platform XYZ? === | ||
| + | |||
| + | === Is it hard to tailor JWT to my needs? === | ||
| + | |||
| + | === I want to see it in action === | ||
| + | * demo | ||
| − | === | + | === What is the future of JWT? === |
== Benefits of JWT == | == Benefits of JWT == | ||
Revision as of 10:37, 27 April 2009
Contents
Questions & Answers
Is JWT just another graphical business process editor?
No! Java Workflow Tooling aims to support the whole BPM lifecycle reaching from the designing of workflows to their execution and monitoring.
So what is the goal of this project?
The goal of the JWT project is to offer vendors an open and flexible framework that can be adjusted to their needs. JWT is designed to be easily extensible and can therefore be made to work together with a variety of different existing tools and standards.
Why should I use JWT instead of tool XYZ?
JWT does not need to replace an existing tooling but can instead be considered to be a framework that brings together different programs and standards and may be used to bridge incompatibilities and add additional functionality.
Can I use JWT with my platform XYZ?
Is it hard to tailor JWT to my needs?
I want to see it in action
- demo
What is the future of JWT?
Benefits of JWT
- Can be combined with vendor tools
design time, development time and runtime workflow tools provide a complete, flexible, interoperable Business Process Management platform. extensible architecture allowing to support many different BP representations, format languages and execution engines. "Distribution"-like releases with specific extensions targeting specific platforms or problems, e.g. JWT for SOA