AW: AW: [smila-dev] section on "when to use" to wiki forprocessingservic

[<Daniel.Stucky@xxxxxxxxxxx>]

Hi Georg,

this should be managed transparently by OSGi DeclarativeServices. If a service X is updated it is first deactivated.
Now it depends how the references to service X are configured. If the reference is required, then a service using X is also deactivated (and so on). If the reference is optional then the service using X is not deactivated. Any method calls that internally make optional use of X will work differently as before (e.g. they may throw exceptions). This is the case for the WorkflowEngine. References to ProcessingServices are not required, so the Workflow engine is not deactivated. If a pipeline is executed where the deactivated ProcessingService is used it will result in an exception.

Of course we could think about a different handling in the workflow engine, at first checking if all needed Services are available and only then execute the pipeline.


Does that answer your question ?

Bye,
Daniel


> -----Ursprüngliche Nachricht-----
> Von: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-
> bounces@xxxxxxxxxxx] Im Auftrag von Georg Schmidt
> Gesendet: Freitag, 24. April 2009 14:17
> An: Smila project developer mailing list
> Betreff: Re: AW: [smila-dev] section on "when to use" to wiki
> forprocessingservices
> 
> Hi Daniel,
> 
> thanks for these guidelines.
> 
> How do you think of the life cycle of a processing service in
> conjunction with the update process of such a service? E.g. how do you
> find all users of that service and how do you restart them after the
> update process?
> 
> Are there already thoughts going on in that area?
> 
> Update process <-> Pipelining, ...
> 
> Kind Regards,
> 
> Georg
> 
> 
> Daniel.Stucky@xxxxxxxxxxx wrote:
> > Hi all,
> >
> > I've added section 3 "When to use a ProcessingService" to page
> http://wiki.eclipse.org/SMILA/Documentation/Pipelets_and_ProcessingServ
> ices.
> > I've also added links to this page on pages
> > -
> http://wiki.eclipse.org/SMILA/Development_Guidelines/How_to_write_a_Pip
> elet
> > -
> http://wiki.eclipse.org/SMILA/Development_Guidelines/How_to_write_a_Pro
> cessingService
> >
> > Feel free to add links on other pages or add comments.
> >
> > Bye,
> > Daniel
> >
> >
> >> -----Ursprüngliche Nachricht-----
> >> Von: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-
> >> bounces@xxxxxxxxxxx] Im Auftrag von Ivan Churkin
> >> Gesendet: Freitag, 24. April 2009 08:07
> >> An: Smila project developer mailing list
> >> Betreff: Re: [smila-dev] section on "when to use" to wiki
> forprocessing
> >> services
> >>
> >> Hi,
> >>
> >> about processing service...
> >> pipelets now is possible to configure by a set of parameters.
> >> its good to have ability to pass parameters to processing service
> >>
> >> guess its quite easy to implement
> >> just additional parameter to interface of PipeletConfiguration type
> and
> >> pass it from pipeline
> >>
> >> --
> >> Regards, Ivan
> >>
> >>
> >> Thomas Menzel wrote:
> >>
> >>> hi,
> >>>
> >>>
> >>>
> >>> i think we should add a section on when to use a processing service
> >>>
> >> in
> >>
> >>> contrast to a normal pipelet.
> >>>
> >>>
> >>>
> >>> my guess is, that the motivation is
> >>>
> >>> - in regard to startup/creation times
> >>>
> >>> - state needs to be kept beyond pipelets life cycle
> >>>
> >>>
> >>>
> >>> any volunteers?
> >>>
> >>>
> >>>
> >>> Kind regards
> >>>
> >>> Thomas Menzel @ *brox *IT-Solutions GmbH
> >>>
> >>>
> >>>
> >>> -------------------------------------------------------------------
> --
> >>>
> >> ---
> >>
> >>> _______________________________________________
> >>> smila-dev mailing list
> >>> smila-dev@xxxxxxxxxxx
> >>> https://dev.eclipse.org/mailman/listinfo/smila-dev
> >>>
> >>>
> >> _______________________________________________
> >> smila-dev mailing list
> >> smila-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/smila-dev
> >>
> > _______________________________________________
> > smila-dev mailing list
> > smila-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/smila-dev
> >
> 
> _______________________________________________
> smila-dev mailing list
> smila-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/smila-dev