title: Mule synchronous callout with message unchanged
body: <p>Mule 3.3.1 Community Edition.</p>
  
  <p>I want to know if I'm missing some simple configuration pattern in Mule that will allow me to do the following general type of process.  I want a message to come in from an inbound endpoint.  I then want to call out to some other endpoint, such as a route-determination service, and, based upon the results of that outbound call, send the original message...unchanged...to a second outbound endpoint.</p>
  
  <p>The call out to the route service changes the original message.  Using constructs like wire-tap seem to pose sequencing problems.  I can do it by copying all the headers and payload, but that's to tedious to code every time I need it and awkward to read.  I can do it quite simply by writing a custom transformer that sets a result variable back on the message.  </p>
  
  <p>But, is there some simple, "pure-Mule-flow" solution for this?  It seems somewhat analogous to the rationale for the http-proxy pattern construct, not having to copy all the inbound stuff to outbound manually.</p>