FYI there are some docs on the composed message processor here http://camel.apache.org/composed-message-processor.html
as well as a unit test here http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/ComposedMessageProcessorTest.java On Sun, Apr 19, 2009 at 7:16 PM, Frank Schwarz <[email protected]> wrote: > > Hi Roman, > > thank you for the clarification. > > For the record, I realized the splitting this way, using the message-id > from > the original message as the aggregation-correlation-id: > > <route> > <from uri="jms:queue:..." /> > <setHeader headerName="MyCorrelationId"><simple>id</simple></setHeader> > <split> > ... > </split> > </route> > > However, I think the documentation is incomplete and somewhat misleading at > this point and should be corrected. > > Kind regards, > Frank > > > > RomKal wrote: > > > > Intended behavior and the implemented one is (b) > > > > -- > View this message in context: > http://www.nabble.com/Composed-Message-Processor-tp23127178p23127659.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Cheers, Jon http://janstey.blogspot.com/
