[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jwt-dev] Beginning of a monitoring plug-in
|
I had a chance to look at your proposal and have a couple of comments
for discussion. From your email, I was under the impression that the
proposal was for monitoring the state of a worflow, but looking at
your proposal, you describe an interface for management of the
worflow. Your proposed worflow service API talks about projects,
process and activity, yet my proposed workflow engine has no projects,
workflow components, and a composite. I don't quite see how the two
would map. If you want to propose a workflow management service, I
think much more discussion is needed. I'm by no means an expert in
this area, but I'm happy to participate where I can. I like the idea
of a workflow service, but I don't currently see how a generic service
could be defined that would be useful.
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.
