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"
(New page: = Benefits of JWT =) |
m (→Benefits of JWT) |
||
| Line 1: | Line 1: | ||
| + | == Why use JWT instead of vendor tools == | ||
| − | = Benefits of JWT = | + | * Can be combined with vendor tools |
| + | |||
| + | |||
| + | == 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 | ||
Revision as of 10:16, 27 April 2009
Why use JWT instead of vendor tools
- Can be combined with vendor tools
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