Hi, I am currently using a recipientList with parallel processing and streaming option with a custom aggregator strategy.
Exchange.MULTICAST_COMPLETE property read on aggregation seems to rely on the recipient list order instead of the order in which they are aggregated. For instance if in recipient list there are ENDPOINT1,ENDPOINT2,ENDPOINT3 and they complete processing (hits aggregator)in following order ENDPOINT2,ENDPOINT3,ENDPOINT1 the property Exchange.MULTICAST_COMPLETE on each exchange (newExhange param) will be populated as false,true,false same is for Exchange.MULTICAST_INDEX. Is there a built in way to know which is the last aggregation exchange in such situation? -- View this message in context: http://camel.465427.n5.nabble.com/Aggregator-Exchange-MULTICAST-COMPLETE-recipientList-tp5715630.html Sent from the Camel - Users mailing list archive at Nabble.com.
