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 (→Why use JWT instead of vendor tools) |
m (→Why should I use JWT instead of tool XYZ) |
||
| Line 1: | Line 1: | ||
| − | === Why should I use JWT instead of tool XYZ === | + | === Is JWT just another graphical editor? === |
| + | |||
| + | |||
| + | === Why should I use JWT instead of tool XYZ? === | ||
* Can be combined with vendor tools | * Can be combined with vendor tools | ||
| + | |||
| + | |||
| + | === Why should I use JWT instead of tool XYZ === | ||
== Benefits of JWT == | == Benefits of JWT == | ||
Revision as of 10:19, 27 April 2009
Contents
Is JWT just another graphical editor?
Why should I use JWT instead of tool XYZ?
- Can be combined with vendor tools
Why should I use JWT instead of tool XYZ
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