| AW: [jwt-dev] JWT Version 0.7 - Draft for a press release and blog entry |
|
Hi all, The Eclipse project Java Workflow Tooling
(JWT) released version 0.7 which is available for download now. JWT aims to
build design time, development time and runtime workflow tools and to foster an
ecosystem of interoperable Business Process Management (BPM) platforms. A new release of the Eclipse
project Java Workflow Tooling (JWT) is now available for download. JWT aims to
build design time, development time and runtime workflow tools and to foster an
ecosystem of interoperable Business Process Management (BPM) platforms. (well, it’s basically
the same just in a different order ;) ) Besides the mentioned changes, the project
team implemented an improved aspect handling, committed several bugfixes and
improved the performance of JWT significantly. Aside from an
improved support for aspect-oriented model extensions and significant improvements
in performance and stability, the 0.7 release provides… (I would put that
already here) The main features of the new release are: -
The underlying metamodel has
been outsourced: view specific information as well as layouting data are
now stored in an own file and separated from the original model (similar as in
GMF). This makes the workflow files much smaller and easier to handle for
existing model-to-model transformations (e.g. from and to BPMN or to STP-IM) as
well as for model-to-text transformations (generating XPDL code, BPEL code,
etc.). -
Automatic layout mechanisms for workflow and process models: JWT does now include layout
algorithms for formatting the shown workflow model in different ways. Workflow
models can be arranged based on an horizontal tree, vertical or using a Spring
theme. These and other layout algorithms from the Eclipse project Zest have
been integrated into JWT. -
New converter: Old versions of JWT are now converted into version 0.7 using ATL
transformations. While the old converter transformed the model elements using
Java code, the new converter allows an easy adaptation to future changes of the
metamodel. …an independent
meta model which allows developers to process JWT workflows without causing
unnecessary dependencies. View specific data like coordinates are now stored in
a separate diagram file which makes the original files not only more robust but
also much lighter and easier to handle. Model Transformations, like from and to
BPMN, BPEL or the STP project’s Intermediate Model are therefore easier
to implement and maintain. To improve the visual
representation of workflows, multiple layout information can now be stored for
each element in the model. Also, automatic layout algorithms which have
been imported from the popular GEF Zest project finally remove the need of tedious
rearranging of positions. Owing to a sophisticated
ATL-based converter, full support for workflow files from previous
versions of JWT is guaranteed. A solid base for future extensions of the meta
model, it can also be used to enhance JWT with the ability to support custom model
aspects. (In my opinion, a
connected text would look better then bullet points, but this is only a personal
preference. However, I think we shouldn’t go into too much technical details
here and go a bit high-level since I guess a pr release should sound good but
don’t carry too much in-depth information. Whats your opinion on this?) Version 0.7 is a joint release by developers
of the University of Augsburg and the French company OpenWide SA. The
University of Augsburg is now an official (associate) member of the Eclipse
Foundation. Regards, Chris Von: jwt-dev-bounces@xxxxxxxxxxx
[mailto:jwt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Florian Lautenbacher Hi guys, please find below a draft for the press
release and blog entry for JWT version 0.7 which we release today. Any comments
are welcome. Best regards, Florian --- Title: Java
Workflow Tooling (JWT) 0.7 released Content: The Eclipse project Java Workflow Tooling
(JWT) released version 0.7 which is available for download now. JWT aims to
build design time, development time and runtime workflow tools and to foster an
ecosystem of interoperable Business Process Management (BPM) platforms. The main features of the new release are: -
The underlying metamodel has
been outsourced: view specific information as well as layouting data are
now stored in an own file and separated from the original model (similar as in
GMF). This makes the workflow files much smaller and easier to handle for
existing model-to-model transformations (e.g. from and to BPMN or to STP-IM) as
well as for model-to-text transformations (generating XPDL code, BPEL code,
etc.). -
Automatic layout mechanisms for workflow and process models: JWT does now include layout
algorithms for formatting the shown workflow model in different ways. Workflow
models can be arranged based on an horizontal tree, vertical or using a Spring
theme. These and other layout algorithms from the Eclipse project Zest have
been integrated into JWT. -
New converter: Old versions of JWT are now converted into version 0.7 using ATL
transformations. While the old converter transformed the model elements using
Java code, the new converter allows an easy adaptation to future changes of the
metamodel. Besides the mentioned changes, the project
team implemented an improved aspect handling, committed several bugfixes and
improved the performance of JWT significantly. Version 0.7 is a joint release by developers
of the University of Augsburg and the French company OpenWide SA. The
University of Augsburg is now an official (associate) member of the Eclipse
Foundation. |