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 "Why use JWT"
m (→Why should I use JWT instead of tool XYZ) |
m (→Is JWT just another graphical editor?) |
||
| Line 1: | Line 1: | ||
| − | == | + | == Questions & Answers == |
| + | === Is JWT just another graphical editor? === | ||
=== Why should I use JWT instead of tool XYZ? === | === Why should I use JWT instead of tool XYZ? === | ||
Revision as of 10:20, 27 April 2009
Contents
Questions & Answers
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