Hi Thomas, ad 1) That route and the use case behind it is not performance critical at all. Right now I am already doing a hybrid of what you proposes. I split from the zip, transform the data from something crude and proprietary to Json and then aggregate to determine completeness and split and REST POST after that. It`s just a couple of items, *once* a week. To sum this question up, I will keep it the way it is. Parallelism may be introduced if the need arises.
ad 2) That thought came up purely for seperation of concerns and because I caught myself wondering where in the the route I set those http headers weeks ago. A simple rename of the splitter class will clear this up enough I think. Thanks Thomas! -- View this message in context: http://camel.465427.n5.nabble.com/Splitter-EIP-Best-Practice-tp5782787p5782817.html Sent from the Camel - Users mailing list archive at Nabble.com.
