[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: AW: [jwt-dev] JWT2XPDL transformation
|
Hi,
Sorry for the fatal error: the package name of CustomXslFunctions in the
XSL files was wrong. I have fixed it.
I can't work on JWT this month, I will treat the other problems
(hooks...) as soon as possible.
Best regards,
Guillaume
Florian Lautenbacher a écrit :
Hi,
when I test the JWT2XPDL transformation, an empty XPDL file is
generated and I get on the console the following messages:
Compiler warnings:
line 103: Attribute 'name' outside of element.
ERROR: 'The first argument to the non-static Java function
'declareName' is not a valid object reference.'
FATAL ERROR: 'Could not compile stylesheet'
Do you know, Guillaume, what I make wrong? I tried it first with very
complex models and in the end with a model having one InitialNode, one
action and one FinalNode and that's it :-) So I guess that one should
probably work.
Concerning the hooks: is there a special element that we shall include
into the metamodel? We are currently discussing of including a generic
"Property" element into the metamodel so that all kind of additional
information could be modeled which are not possible right now - would
this help? Another way right now would be to use the comment function
that can be attached to each model element (To an action, an activity,
etc.). But right now, this is only visible and editable in the outline
view and not in the graphical editor itself.
Best regards,
Florian
------------------------------------------------------------------------
*Von:* jwt-dev-bounces@xxxxxxxxxxx
[mailto:jwt-dev-bounces@xxxxxxxxxxx] *Im Auftrag von *Miguel Valdes Faura
*Gesendet:* 23 March 2008 23:17
*An:* 'Java Workflow Toolbox'
*Betreff:* RE: [jwt-dev] JWT2XPDL transformation
Hi,
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 ?
Regards,
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: http://orchestra.objectweb.org
*Bonita*, The XPDL open source project: http://bonita.objectweb.org
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.
Guillaume
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
>> https://dev.eclipse.org/mailman/listinfo/jwt-dev
>>
>
> _______________________________________________
> jwt-dev mailing list
> jwt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jwt-dev
>
>
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
------------------------------------------------------------------------
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev