Hi Jon,

thank you for the pointers.

I did indeed have a look these pages, and I think there can be enhanced as
well.

If a beginner looks at this line:
from("seda:aggregate").aggregate(new
MyOrderAggregationStrategy()).header("orderId").to("mock:result");

it is nowhere clear, what the header("orderId") refers to. Even in the
source code of the unit test, you have to know where to look for.

Please, see this a as a RFE.

Please also consider enhancing the first user experience of the splitter
component by adding a default correlation id, that can eventually be picked
up (by default) by an aggregation component later on.

-- Frank




janstey wrote:
> 
> 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
> 
> -- 
> Cheers,
> Jon
> 
> http://janstey.blogspot.com/
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Composed-Message-Processor-tp23127178p23130624.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to