In continuation of the ‘Mule Tutorial Series’, this blog post intends to explain the use of all flow control component.
So far the HTTP endpoint demonstrated in this tutorial series had inbound HTTP endpoints. The HTTP endpoint also supports outbound endpoint. This example illustrates two functionalities one displays use of HTTP endpoint as outbound endpoint and second demonstrates the ‘fork and join’ flow control.
In my previous blog post, CSV to Maps component was used to convert the CSV input to Java Maps. The CSV to Maps component loads the entire CSV content in memory before transforming into Maps. In case the file is large, this approach would lead to large memory consumption. Mule provides a memory efficient solution using the DataMapper component.
A typical Mule application is built around one or more flows. The flow receives a message; the message progresses thru one or multiple steps/activities which perform specific tasks/actions. The flow consists of message sources (endpoints) and then message processors(endpoints, scopes, components, transformers, filters, flow controls, error handlers).