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.

+

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, standards and runtimes.

=== Why should I use JWT instead of tool XYZ? ===

=== Why should I use JWT instead of tool XYZ? ===

Line 14:

Line 14:

=== Can I use JWT with my platform XYZ? ===

=== Can I use JWT with my platform XYZ? ===

+

+

Currently JWT has been tested successfully with the [http://wiki.bonita.ow2.org/xwiki/bin/view/Main/News Bonita] process engine in combination with the [https://wiki.objectweb.org/frascati/Wiki.jsp?page=FraSCAti FraSCAti] SCA platform.

+

The JWT tools can be adapted for other platforms as well.

=== Is it hard to tailor JWT to my needs? ===

=== Is it hard to tailor JWT to my needs? ===

−

=== I want to see it in action ===

+

No! The workflow editor offers a variety of extension points that are documented [[http://wiki.eclipse.org/JWT_Extensions here]] that allow to extend and modify the way JWT works without actually needing to change JWT itself (which can of course also be done if needed).

+

+

=== I want to see it in action! ===

A demo screencast that shows how a business process can be imported into JWT, extended with technical information and run on a workflow engine can be seen [http://www.eclipse.org/jwt/press/eclipsecon09/EclipseCon09Example.swf here].

A demo screencast that shows how a business process can be imported into JWT, extended with technical information and run on a workflow engine can be seen [http://www.eclipse.org/jwt/press/eclipsecon09/EclipseCon09Example.swf here].

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, standards and runtimes.

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?

Currently JWT has been tested successfully with the Bonita process engine in combination with the FraSCAti SCA platform.
The JWT tools can be adapted for other platforms as well.

Is it hard to tailor JWT to my needs?

No! The workflow editor offers a variety of extension points that are documented [here] that allow to extend and modify the way JWT works without actually needing to change JWT itself (which can of course also be done if needed).

I want to see it in action!

A demo screencast that shows how a business process can be imported into JWT, extended with technical information and run on a workflow engine can be seen here.