camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-1550) Improve first user experience of a composed message processor
Date Mon, 18 May 2009 07:18:50 GMT


Claus Ibsen commented on CAMEL-1550:

I have updated the wiki page with a note on the correlation expression using header(orderId).

The splitter already insert an INDEX and TOTAL headers and it has in fact a build in aggregator
as well. But since the EIP pattern indicate to use a splitter and aggregator Jonathan created
the sample according to this fact. However this build in aggregator is only useable for *inOut*
(request/reply) messaging.

We do have some rough ideas to improve the splitter, resequencer and aggregator in the future
so its aggregation can more easily be configured to use a sequence of exchanges generated
by a poller, eg. for instance a filer poller. So we can aggregate the files that was polled
by default.


> Improve first user experience of a composed message processor
> -------------------------------------------------------------
>                 Key: CAMEL-1550
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core, documentation, examples
>    Affects Versions: 2.0-M1
>            Reporter: Frank Schwarz
>             Fix For: 2.0.0
> With some little changes, the pattern "composed message processor" could be realized
more easily. I am proposing to let the splitter component by default insert on each of its
output-messages the message id of its input-message as a standardized header. The aggregator
component then should, if nothing else is specified, use this header as a correlation id for
the aggregation. So, the splitting-aggregation-stuff works out-of-the box.
> see also:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message