title: Passing body message outside the scope in Camel
body: <p>Till now, my experience told me that the body in message is always changed with any processing on it. So for now I always process data and finally the result always appear on the body where I can take it for further processing.</p>
  
  <p>Currently I'm experiencing something strange - or, not strange, but something which I didn't use to.</p>
  
  <p>I'm using following route</p>
  
  <pre><code>&lt;route&gt;
    &lt;from uri="activemq:queue:add"/&gt;
    &lt;split&gt;
      &lt;simple&gt;${body}&lt;/simple&gt;
      &lt;bean ref="pool" method="add(${body.getId},${body.getText})"/&gt;
      &lt;log loggingLevel="INFO" message="GOOD BODY ${body}"/&gt;
    &lt;/split&gt;
    &lt;log loggingLevel="INFO" message="BAD BODY of type of argument of add method ${body}"/&gt;
  &lt;/route&gt;
  </code></pre>
  
  <p>and I want at least access the result of add method as it is shown in GOOD BODY log, but finally the body later on is for some reason exchanged with the original type of argument of called method add.</p>
  
  <p>I'm working here on split ArrayList, but anyway finally I need just one result for single entry. Also I need to add all objects on the list with add method, so I can not work on single entry only.</p>
  
  <p>How can I pass the result of "internal" processing to pass it outside back to the originating calling route?</p>