camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Moulliard <>
Subject Information required about IN/OUT pattern of splitter EIP
Date Tue, 16 Jun 2009 12:11:35 GMT

I'm a little confused about the split EIP pattern combined with aggregation
strategy. In the example (see - Split
aggregate request/reply sample), the out exchange is used to retrieved the
body content and also to set it because the pattern is of type InOut.

I have created an aggregator but in my case, I must use the content of the
In to retrieve my body

        List requestMessages = new ArrayList();

        if (oldExchange == null) {

            return newExchange;
        } else {
            // Get old messages
            requestMessages = oldExchange.getIn().getBody(List.class);

            // Get new and add it to the list


            // Add to the exchange
            return oldExchange;


Questions :
- Is the split EIP an InOut pattern ?
- When I develop the aggregator like this, the headers of my messages have
disappeared when the endpoint called after the end of the split receives the
List of Objects. How can I avoid this ?


Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

blog :

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message