Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: neutral (athena.apache.org: 124.108.96.112 is neither permitted
 nor denied by domain of rahul.thakur.xdev@gmail.com)
Message-ID: <47E64198.3030001@gmail.com>
Date: Mon, 24 Mar 2008 00:40:08 +1300
From: Rahul Thakur <rahul.thakur.xdev@gmail.com>
User-Agent: Thunderbird 3.0a1pre (Windows/2008032202)
MIME-Version: 1.0
To: dev@continuum.apache.org
Subject: Re: [Discuss] Workflow engine
References: <47DF0892.4060203@gmail.com>
 <47DF22F2.9030409@gmail.com>	 <a43524d00803180926j365b4b98y152201ea5a22955e@mail.gmail.com>
	 <5d3354e30803192138v7a173a91od4680ca434049550@mail.gmail.com>
	 <a43524d00803201013l5e096934h64a80aee24b87b84@mail.gmail.com>
 <f345f3480803210302l2afc9bfag8df1654a9209f933@mail.gmail.com>
In-Reply-To: <f345f3480803210302l2afc9bfag8df1654a9209f933@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


I am inclined to "+1" something comprehensively documented and used.

I imagine the workflow compositions to be done by the user and be 
exposed as service for invocation/monitoring/management. A WF engine 
based on petri nets would be neat. Also, I think it might be a better 
idea to persist the WF definitions to an underlying store (DB).

Rahul


Emmanuel Venisse wrote:
> For the moment, I'm -0 for plexus-spe, probably because I don't know one
> project that use it and we don't have a documentation about it.
>
> For next versions of Continuum, I'd like we use external tools known by
> users so it will be more easy to grow our community.
> An other point before to choose a tool is to define what will be the role of
> the workflow in the core. Will it be use only in one Continuum node or will
> can be explode worflow steps on each node when Continuum will be used with
> the distributed mode.
>
> Emmanuel
>
> On Thu, Mar 20, 2008 at 6:13 PM, Jesse McConnell<jesse.mcconnell@gmail.com>
> wrote:
>
>
>> well, no need to do anything from scratch with the plexus-spe stuff, think
>> trygve has used it in a few places.
>>
>> jesse
>>
>> On Wed, Mar 19, 2008 at 9:38 PM, Rahul Thakur<rahul.thakur.xdev@gmail.com
>>
>> wrote:
>>
>>
>>> Yeah, my idea was to refactor and wrap up current tasks/actions in the
>>> build controller into a workflow and get that to work first.
>>>
>>> There are other possibilities, of course, having user defined build
>>> workflows and ability to invoke them remotely.
>>>
>>> Any suggestions for a WF engine? I am not sure if implementing
>>> something from scratch is a good idea.
>>>
>>> Cheers,
>>> Rahul
>>>
>>>
>>> On Wed, Mar 19, 2008 at 5:26 AM, Jesse McConnell
>>> <jesse.mcconnell@gmail.com>  wrote:
>>>
>>>> probably a good idea to bring this up now
>>>>
>>>> originally I think the idea was to implement workflow with the
>>>>
>>> plexus-spe
>>>
>>>> component which is in the plexus sandbox but that is up for debate, or
>>>> whoever takes the bull by the horns and started implementing. :)
>>>>
>>>> cheers!
>>>> jesse
>>>>
>>>> On Mon, Mar 17, 2008 at 9:03 PM, Rahul Thakur<
>>>>
>>> rahul.thakur.xdev@gmail.com>
>>>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>> I found this:
>>>>> http://java-source.net/open-source/workflow-engines
>>>>>
>>>>>
>>>>> Rahul Thakur wrote:
>>>>>
>>>>>> Hello everyone!
>>>>>>
>>>>>> As a part of architecture rework and having a workflow engine at
>>>>>>
>> the
>>
>>>>>> heart of Continuum, we need to decide on a Workflow engine
>>>>>> implementation that we can use.
>>>>>>
>>>>>> Does anyone know any WF engines to put forth as candidates (+
>>>>>>
>>> features
>>>
>>>>>> provided, how we can leverage them for Continuum... etc)
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> Cheers,
>>>>>> Rahul
>>>>>>
>>>>>>
>>>>
>>>> --
>>>> jesse mcconnell
>>>> jesse.mcconnell@gmail.com
>>>>
>>>>
>>
>> --
>> jesse mcconnell
>> jesse.mcconnell@gmail.com
>>
>>
>
>