Hi Peter,

First of all: nice name! :)

Secondly: I read your blog item, but I don't think that is what we are looking 
for, unless I misunderstood something. What we are looking for is a way to 
understand what happened in the separate services to be able to create a report 
of a end2end work flow that starts in one end and ends up in another end of the 
application. Our current approach is that we pass on a WorkFlow that then 
records its own steps about success/failure. However, because of this we needed 
to modify the service interface to include this WorkFlow interface in the 
method.

/Peter


On 29 nov 2010, at 19.00, osgi-dev-requ...@mail.osgi.org wrote:

> Message: 4
> Date: Mon, 29 Nov 2010 14:45:49 +0100
> From: Peter Kriens <peter.kri...@aqute.biz>
> Subject: Re: [osgi-dev] Work flow control
> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org>
> Message-ID: <cf43adda-0fb6-4472-a209-94bd94bab...@aqute.biz>
> Content-Type: text/plain; charset=us-ascii
> 
> We are currently working on a Coordinator API that seems useful in your case: 
> http://www.osgi.org/blog/2010/06/to-coordinate-in-osgi.html
> 
> It depends a bit on what your timing is because the Coordinator is for not so 
> long lived tasks. If you want to extend the life time you probably need 
> something like workflow engine.
> 
> Kind regards,
> 
>       Peter Kriens
> 
> On 27 nov 2010, at 09:19, Peter Lauri wrote:
> 
>> Hi,
>> 
>> We have a software that contains of multiple bundles that perform some 
>> specific tasks that are being connected via service interfaces. The flow of 
>> the application is that data enters via one service interface and then 
>> output is given via another service interface. Now for the complete flow we 
>> need to give an summary report of the process, as some if the intermediate 
>> bundles performs tasks that are of important to know if sub tasks are 
>> successful or not. 
>> 
>> Is there any standard of doing this in OSGi? Our last way out is to include 
>> our own WorkFlow interface that we pass to the components of interest and 
>> they need to fill these ones out. 
>> 
>> With regards,
>> Peter lauri
>> _______________________________________________
>> OSGi Developer Mail List
>> osgi-dev@mail.osgi.org
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
> 

_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to