Claus Ibsen-2 wrote: > > Hi > > I have created a ticket to track this issue > https://issues.apache.org/activemq/browse/CAMEL-1702 > > We will *only* do this migration at Camel 2.0 to keep the old behavior > in Camel 1.6.x as this branch is maintenance and for important bug > fixes only. > Its intended for drop in replacements for production usage and this we > cannot change such behavior. Even if it would make life easier. > > >
The ticket mentions automatic fallback from header -> property. That is not available in 1.6.x as far as I know. That would solve half of the workaround. It is a possibility to use header OR property for aggregation? That would not really break existing implementations because the whole camel namespace is used in the property. The current splitter / aggregation implementation is really fragile without good knowleds of camel 1.6.x Regards, Erwin -- View this message in context: http://www.nabble.com/Custom-AggregationStrategy-needs-specific-headers-tp23996092p24000219.html Sent from the Camel - Users mailing list archive at Nabble.com.
