Jump to: navigation, search


< SMILA‎ | Documentation
Revision as of 04:43, 26 September 2008 by Daniel.stucky.empolis.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page describes Pipelets, ProcessingServices and their lifecycle.


Pipelets and ProcessingServices are reusable Java Components in a BPEL workflow and can be orchestrated like any regular BPEL Service. Both are used to process the data contained in [[[SMILA/Glossary#R|Records]].


A Pipelet is a POJO that implements the interface org.eclipse.smila.processing.SimplePipelet. It's lifecycle and configuration are managed by the workflow engine. An instance of a Pipelet is not shared by multiple Pipelines (workflows), even multiple invocations of a Pipelet in the same Pipeleline do not share the same instance. Each <invokePipelet>Pipeline has it's own instance. An instance may still be accessed by multiple threads, for example if the same Pipeline is executed in parallel. Technical details on Pipelet development can be found in the tutorial How to write a Pipelet.


A ProcessingServices is an OSGi service (preferably a Declarative Services) that implements the interface org.eclipse.smila.processing.ProcessingService. It's lifecycle and configuration are NOT managed by the workflow engine, but by the OSGi runtime. An instance of a ProcessingService can be shared between multiple Pipelines and so are frequently accessed by multiple threads. Technical details on ProcessingServices development can be found in the tutorial How to write a ProcessingService.

Pipelet Lifecycle

Lifecycle of Pipelets.png

ProcessingService Lifecycle

Lifecycle of ProcessingServices.png

Combined Lifecycle

Lifecycle of Pipelets and ProcessingServices.png