Uses of Interface
org.mule.api.construct.Pipeline

Packages that use Pipeline

org.mule.construct
org.mule.context.notification	Internal server notification types fired via the MuleManager.

Uses of Pipeline in org.mule.construct

Classes in org.mule.construct that implement Pipeline

class	AbstractConfigurationPattern A template class for configuration patterns, which takes care of setting common message processors and optional transformers defined on the pattern.
class	AbstractPipeline Abstract implementation of AbstractFlowConstruct that allows a list of AbstractPipeline.ProcessIfPipelineStartedMessageProcessors that will be used to process messages to be configured.
class	Bridge A simple bridge between a single inbound endpoint and a single outbound endpoint.
class	Flow This implementation of AbstractPipeline adds the following functionality: Rejects inbound events when Flow is not started Gathers statistics and processing time data Implements MessagePorcessor allowing direct invocation of the pipeline Supports the optional configuration of a ProcessingStrategy that determines how message processors are processed.
class	SimpleService In-out SOA-style simple service, with no outbound router.
class	Validator

Uses of Pipeline in org.mule.context.notification

Constructors in org.mule.context.notification with parameters of type Pipeline

AsyncMessageNotification(Pipeline pipeline, MuleEvent event, MessageProcessor messageProcessor, int action)

AsyncMessageNotification(Pipeline pipeline, MuleEvent event, MessageProcessor messageProcessor, int action, MessagingException exception)

PipelineMessageNotification(Pipeline pipeline, MuleEvent event, int action)

PipelineMessageNotification(Pipeline pipeline, MuleEvent event, int action, MessagingException exception)