A template class for configuration patterns, which takes care of setting common message processors and optional transformers defined on the pattern.
A simple bridge between a single inbound endpoint and a single outbound endpoint.
Experimental implementation that supports a single dynamic pipeline due to restrictions imposed by intercepting message processors and their lifecycle.
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.
The lifecycle manager responsible for managing lifecycle transitions for a Mule service.
In-out SOA-style simple service, with no outbound router.
Copyright © 2003–2015 MuleSoft, Inc.. All rights reserved.