Improve first user experience of a composed message processor
-------------------------------------------------------------

                 Key: CAMEL-1550
                 URL: https://issues.apache.org/activemq/browse/CAMEL-1550
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-core, documentation, examples
    Affects Versions: 2.0-M1
            Reporter: Frank Schwarz


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: http://www.nabble.com/Composed-Message-Processor-td23127178s22882.html

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

Reply via email to