Thanks for your response; I'm sorry I don't fully understand your example.  I
looked at recipient list, but that seems to be for sending to multiple
endpoints vs. a single endpoint with a mutated value.  Basically, I'd like
to loop through the values in a "split" header and send a message to the
same endpoint  for each one (onPrepare looked interesting, but still didn't
get me there).  

Due to the lack of response I'm guessing this is pretty far out of standard
practice so I'm now trying to get the service provider to just accept my
list of values and parse it service-side (so just one call to the endpoint
as I am doing now)

--
View this message in context: 
http://camel.465427.n5.nabble.com/Best-Practice-for-splitting-on-header-tp5713433p5713756.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to