Home » Software Development » ForEach vs Splitter in mule

About Abhishek Somani

Abhishek Somani
Abhishek is working as a senior java developer in a product start up .He has worked on various java related enterprise applications and frameworks. He loves to explore new technologies

ForEach vs Splitter in mule

This example app will show the difference between Foreach and splitter in Mule version 3.x. Collection splitter splits the incoming collection object and then you have to put a aggregator to collect the resultant objects. For each scope is a scope which does not change the payload and you get the same collection object once for each loop completes.

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:vm="http://www.mulesoft.org/schema/mule/vm" xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
 xsi:schemaLocation="http://www.mulesoft.org/schema/mule/vm http://www.mulesoft.org/schema/mule/vm/current/mule-vm.xsd
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd">
    <http:listener-config name="HTTP_Listener_Configuration" host="" port="8081" doc:name="HTTP Listener Configuration"/>
    <flow name="foreachtestFlow">
        <http:listener config-ref="HTTP_Listener_Configuration" path="/test" allowedMethods="GET" doc:name="HTTP"/>
        <component class="foreachexample.CollectionPayloadComponent" doc:name="Java"/>
        <!-- <foreach doc:name="For Each">
         <choice doc:name="Choice">
         <when expression="#[payload == 'foreach']">
          <set-session-variable value="foreachVar" variableName="test" doc:name="Session Variable"></set-session-variable>
          <set-session-variable value="BBQVar" variableName="test" doc:name="Session Variable"></set-session-variable>
         <flow-ref name="flow3" doc:name="Flow Reference"/>
        </foreach> -->
        <collection-splitter />
        <logger message="payload is : #[payload]" level="ERROR"/>
         <when expression="#[payload == 'foreach']">
          <set-session-variable value="foreachVar" variableName="test"></set-session-variable>
          <set-session-variable value="BBQVar" variableName="test"></set-session-variable>
        <flow-ref name="flow3" />
   <set-payload value="dsadasd"/>        
    <flow name="flow2">
        <vm:inbound-endpoint path="foreach" doc:name="VM"/>
        <logger message=" session var value is #[sessionVars.test] and payload is #[payload]" level="ERROR" doc:name="Logger"/>

 <flow name="flow3">
        <vm:outbound-endpoint path="foreach" doc:name="VM"/>

Post your comments and suggestions.

Published on Java Code Geeks with permission by Abhishek Somani, partner at our JCG program. See the original article here: ForEach vs Splitter in mule

Opinions expressed by Java Code Geeks contributors are their own.

(0 rating, 0 votes)
You need to be a registered member to rate this.
Start the discussion Views Tweet it!
Do you want to know how to develop your skillset to become a Java Rockstar?
Subscribe to our newsletter to start Rocking right now!
To get you started we give you our best selling eBooks for FREE!
1. JPA Mini Book
2. JVM Troubleshooting Guide
3. JUnit Tutorial for Unit Testing
4. Java Annotations Tutorial
5. Java Interview Questions
6. Spring Interview Questions
7. Android UI Design
and many more ....
I agree to the Terms and Privacy Policy

Leave a Reply


This site uses Akismet to reduce spam. Learn how your comment data is processed.

Notify of