Hi, I am trying to realize a composed message processor - without luck so far.
The messages get perfectly split, but I am not sure, how to realize the aggregation later on. Is there any built-in correlation criteria for the aggregation? The documentation (http://camel.apache.org/splitter.html) says: CamelSplitIndex: Camel 2.0: A split counter that increases for each Exchange being split. The counter starts from 0. How shall I read this line? (a) For each composed message that is split, every item (that results from the split) gets the _same_ value for the header "CamelSplitIndex". For the next composed message to be split, this counter is increased by 1. (b) For each split item from a composed message the header "CamelSplitIndex" is increased by 1. With every new composed message to be split, this counter start from 0. I understand the documentation as (a) but what I observe is (b). What is the correct reading? What is the intended behavior? If (b), why does the splitter not insert a correlation header for the aggregation later on? Kind regards, Frank -- View this message in context: http://www.nabble.com/Composed-Message-Processor-tp23127178p23127178.html Sent from the Camel - Users mailing list archive at Nabble.com.
