Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: [jwt-dev] About workflow integration with JWT
Hi Pablo,
 
JWT is ought to work not only with one specific engine (like Bonita, allthough many examples are currently connected to that one), but with all kinds of process engines or workflow engines. Therefore, we are currently developing extension mechanisms: if some engine does need additional information that cannot be covered with the current metamodel (which is in the process of change anyway, see [1]), then it can be extended with new properties, new node types, etc.
 
The process after that would be similar to what you already described:
 
1) Draw the process model in the JWT Workflow Editor (WE)
2) Add some engine-specific details
3) Export the workflow in a suitable format (this might be XPDL, BPEL or any other language such as the JBoss-specific jPDL)
4) Deploy the workflow on the process engine (we would like to have a mechanism directly in Eclipse for that, but currently didn't have the time for that)
5) Monitor the process on the workflow engine. The jwt-monitoring is a first draft to show that this is possible in Eclipse, but still dependant on Bonita, other implementations will come and are welcome from contributors, of course, too.
6) Concerning the jwt-runtime-api: this has been created as part of a French research project called SCOrWare. Since I have not been involved here, others are problably better to comment on that (Marc, Mickael?).
 
Best regards and a happy new year,
 
Florian
 
[1] http://following-flo.blogspot.com/2008/12/reviewing-jwt-metamodel.html

Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Pablo Beltran
Gesendet: 28 December 2008 06:58
An: jwt-dev@xxxxxxxxxxx
Betreff: [jwt-dev] About workflow integration with JWT

Hi,

I would like to integrate other workflow with JWT rather than Bonita and doing only at the graphical level.

Which are the steps to achieve it?

1. Draw the process into the JWT Workflow Editor
2. Export the workflow to the XPDL format
3. Load the XPDL into the external workflow
4. Mapping real users with participants (external workflow)
5. Reflect what is happening via the jwt-monitoring(-test) into Eclipse (like highlight activities, participants, application/tools,...).
6. Not sure about whether using the jwt-runtime-api would be necessary...

Might someone clarify this?

Best regards,
Pablo.




Back to the top