Sorry, this maybe better - using setMsgId()
@Test
public void request01Test() throws Exception {
final PDUBean bean1 = new PDUBean();
bean1.setMsgId("1");
final PDUBean bean2 = new PDUBean();
bean2.setMsgId("2");
PDUBean rslt1 = template.requestBody(bean1, PDUBean.class);
Thanks Claus.
Ok, I have made some changes on my design (daisy-chaining way instead).
From
Maven Camel Project A: from(direct://).
Maven Camel Project B: from(direct://).
Maven Camel Project C: from(direct://).
Maven Camel Project
Main:
from().to(direct://).to(direct://).to(direct://)
To
Hi
A bit hard to explain without having to write endless long emails.
This is expected the aggregator uses a separate "leg" of the routing
when it sends completed outgoing messages. eg its input and output
legs are separated.
On Tue, Jun 23, 2015 at 1:11 PM, Ravi Nallappan
wrote:
> Hi,
>
> I a
Hi,
I am trying to create modular routes that at the end stitched together by a
main route. This strategy is working for most of my other routing except
when I use aggregator.
I have created a simple test case for this scenario:
package com.ravi.test;
import org.apache.camel.Exchange;
import o
