On Fri, Jun 12, 2009 at 4:38 PM, ErwinK<[email protected]> wrote: > > > 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. The fallback is when you use the DSL, eg .header("foo") and not when you do a getHeader directly on the exchange/message.
> > 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. Good idea. We can add the information in both header (as now) and properties (new) in 1.6.2. This will not break anything. > > The current splitter / aggregation implementation is really fragile without > good knowleds of camel 1.6.x The splitter has build in aggregator so often you just let the splitter alone deal with it. See the request/reply splitter sample on the splitter wiki page. Then you do not have to worry about split index and split total etc. If you would like to contribute a patch for 1.6.2. Then I suggest to find an unit test that uses splitter and tests with the SPLIT_INDEX headers. Then take a copy of this class and do a test where you use properties instead. And then look in the Splitter (in the processor) to find where to add the properties as well. > > 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. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
