used to break down an outgoing message into parts and dispatch those parts over different endpoints configured on the router. Then this is the task of aggregator to do just opposite to splitter. An aggregator gets input from various connectors and join them in one flow. The actual endpoint used for each object in the list is determined by a filter configured on the endpoint itself. If the endpoint’s filter accepts the object, the endpoint will be used to route the object.
instance of a user-written class that aggregates messages. This class must implement the interface MessageProcessor. Often, it will be useful for it to subclass AbstractAggregator, which provides the skeleton of a thread-safe aggregator implementation, requiring only specific correlation logic. As with most custom objects in Mule, it can be configured either with a fully specified class name or as a reference to a Spring bean. It can also be configured with the same timeout and failOnTimeout attributes described under Collection Aggregator.
are the options on general tab – Display Name – The name of the component to be displayed in Mule flow. Class – Fully qualified class name of the custom correlation aggregate router to be used. Timeout – The timeout time in milliseconds. Message Info Mapping – Maps the current message attributes with the known message attributes. Store Prefix – Defines the prefix of the object store names.
(Cont.) Following are the options on general tab – Message ID Expression – Expression for mapping message attributes to messageIdExpression. Correlation ID Expression – Expression for mapping message attributes to correlationIdExpression.