Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: [jwt-dev] Beginning of a monitoring plug-in

Hi Mickael,

first of all thanks for your first approach for the monitoring plugin. I
really like it! However, I had a look at the description in the Wiki and
would have some questions:

-Workflow State Model: a workflow engione contains * processes which are
only allowed to contain 1 activity? why not 1..* activities?  
-package structure: Currently you have org.eclipse.jwt.runtime.workflow
which is quite good, but not perfectly compliant with the package structure
we laid out at the beginning of the project. At the beginning we said we'll
have components such as WE, the workflow editor, and WAM the workflow
administration and monitoring toolkit. So it would be good to refactor the
package structure into something like org.eclipse.jwt.wam.monitoring
-with this package structure you could upload it, since it is a component
written by a committer and already announced to the community - so no
problems this time ;-)
-a general question: is the process already deployed on the process engine
or will it be deployed by this monitoring API? There are methods such as
startActivity which sound like you would start one of the activities defined
by the process model. Or maybe I am just confused by the naming ;-) Is
Activity one specific process step or a bunch of process steps and itself a
-I'd love to see something like this together with AgilPro/JWT where we
build on the process engine JBoss jBPM. However, I don't have enough
knowledge how to invoke the process engine and do this monitoring.
Therefore, I added Koen to this discussion thread and would like to ask you,
Koen, for your opinion about such a monitoring component: would jBPM be
compatible with such an API or would you require some changes?

Best regards,


-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Mickael Istria
Gesendet: 22 April 2008 10:36
An: Java Workflow Toolbox
Betreff: Re: [jwt-dev] Beginning of a monitoring plug-in


I added on the wiki page the model that we use for a workflow state. 
This model is part of the workflow service API that must use any extension.
Of course it can be corrected/improved according to other specific features
(it currently fits with Bonita, but we didn't try with other workflow
I also added the code of WorkflowService interface, that we use to get the
state of the workflow.
It might be interesting for you.

In the Bonita remote implementation of this interface, we only use the
"listUserActivities(true, true, login)" method to get all informations about
the state of the workflow. Indeed, calling this method with this attributes
gives us the whole workflow state, since this workflow state is fully
Thus, you're right, it is a poll mechanism, with all the limits that it
involves. (especially the need to refresh to check for modifications)

We are still thinking about an event mechanism, but I'll let Marc tell you
more about this, since he has more knowledge on this subject.


Bryan Hunt a écrit :
> This is interesting.  I've been doing some more work on my EMF 
> workflow model/engine and I'm about to look at modeling state 
> information and the ability to monitor that state.  It sounds like 
> this is using a polling mechanism to monitor the state.  Is that 
> correct?  I'm considering using an event model for state transitions.  
> I would be concerned about using a polling mechanism especially when 
> running the workflow remotely - performance is critical in my intended 
> application.
> Bryan
> On Apr 21, 2008, at 10:56 AM, Mickael Istria wrote:
>> Hello,
>> I've written a little plug-in framework that can be used to monitor a 
>> workflow state from a workflow engine. This is not at all a mature 
>> plug-in for the moment, but I hope it is an interesting base for the 
>> future.
>> Monitoring a workflow engine can be done in a few steps:
>> 1. Implement an interface (WorkflowService) with your favorite 
>> workflow engine. (We use the "Adapter" design-pattern)
>> 2. Make this service accessible to the user who wants to monitor it 
>> in Eclipse (you can use webservices, rmi, or anything you are able to 
>> write a client programmaticaly)
>> 3. Implement an extension plug-in which defines the way to acces the 
>> service (so called a service provider) from inside Eclipse.
>> We are currently able to monitor Bonita via a CXF/Aegis WebService 
>> (see the wiki for screenshots).
>> You can find more detailed information and basis for discussion on 
>> the JWT wiki at
>> Hope you will find it interesting!
>> Regards,
>> Mickael
>> _______________________________________________
>> jwt-dev mailing list
>> jwt-dev@xxxxxxxxxxx
> _______________________________________________
> jwt-dev mailing list
> jwt-dev@xxxxxxxxxxx

jwt-dev mailing list

Back to the top