Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [jwt-dev] JWT2XPDL transformation



First of all congratulations for the last JWT release and the JWT2XPDL transformation. We, at Bonita team, will definitely give it a try (as discussed with Marc last week)!


Just one comment on your last post (Guillaume):


Hooks in Bonita are just java classes so I think that identify them at the JWT editor only by their package name (default is hero.hook but could be different) is not a good idea IMO. For hooks, mappers, performers… any other advanced features provided as an external attribute in XPDL we should add additional data to the model rather than use name conventions, what do you think ?



Miguel Valdes


BPM Manager


Bull, Architect of an Open World TM

1, rue de Provence

38130 Echirolles (France)

Direct Line: +33-4-76-29-72-28

Fax: +33-4-76-29-75-18


*Orchestra*, The BPEL open source project:

*Bonita*, The XPDL open source project:


This e-mail contains material that is confidential for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.


-----Message d'origine-----
De : jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] De la part de Guillaume Decarnin
Envoyé : vendredi 21 mars 2008 18:38
À : Java Workflow Toolbox
Objet : Re: [jwt-dev] JWT2XPDL transformation


If a JWT application is a hook (Java class "hero.hook.*"), it is

translated into a Bonita Hook. But the event is always afterTerminate,

the next version should manage other events.





Marc Dutoo a écrit :

> Very nice job Guillaume !


> And what about Bonita specific features, like Java Hooks ?


> Regards

> Marc


> On Fri, 21 Mar 2008 17:47:53 +0100, Guillaume Decarnin

> <guillaume.decarnin@xxxxxxxxxxx> wrote:


>> Hello,


>> I have commited the JWT2XPDL transformation, for export from JWT to

>> Bonita (path: transformations/jwt-xpdl).


>> This first version has some limitations :

>> - If the JWT workflow has a cycle, Bonita will not be able to load the

>> generated XPDL file. For supporting cycles, the transformation should

>> detect the concerned edge and translate it into an iteration, not a

>> transition.

>> - All the JWT data are converted in process properties instead of

>> activity properties, because of difficulties to manage unique field


> names.


>> - The subprocess calls are not managed. Embedded subprocess are ok.


>> Best regards,

>> Guillaume Decarnin

>> Open Wide


>> _______________________________________________

>> jwt-dev mailing list

>> jwt-dev@xxxxxxxxxxx




> _______________________________________________

> jwt-dev mailing list

> jwt-dev@xxxxxxxxxxx





jwt-dev mailing list


Back to the top