[
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,
I tried the monitoring tool and it looks nice. Since I don't have a process
engine installed on my machine or the knowledge about how to get the current
actions out of a process engine, I can't implement the interface
WorkflowService and therefore I don't have a workflow service provider in my
list (and can't test it completely). However, when looking at the code, I
found that there is still some mixture (at least in plugin.xml) between
org.eclipse.jwt.WAM and org.eclipse.jwt.RUNTIME which you might want to
change in one of the future versions. I guess that's everything I am able to
give you on feedback here.
Best regards,
Florian
-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Mickael Istria
Gesendet: 23 April 2008 14:22
An: Java Workflow Toolbox
Betreff: Re: [jwt-dev] Beginning of a monitoring plug-in
Bryan Hunt a écrit :
> 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 made some refactoring this morning, and I think that the current version
of the monitoring plug-in could allow to add any model that can be
considered as a composite pattern.
I put an archive with some code in
technology/org.eclipse.jwt/wam/monitoring.tgz
Feel free to take a look at it, and ask any question if you want to use it
to monitor MWE.
Currently, we have a model and a composite mapping of this model for the
TreeViewer. Anything that extends WorkflowBeanComposite class can easily be
added to the TreeViewer as a workflow engine.
This way, the architecture can allow several models in the viewer. In the
future, it will probably become an Eclipse extension, but we will talk about
it when we will have enough use cases (to get more concrete ideas).
However, I also think that we should avoid multiplying workflow models in
this monitoring tool, and focus on what is common; maybe to find
*the* generic workflow model...
Mickael
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
