Hi, For starters, I would change the template code to do what is shown in my code stub below
Second, You might want to add a trace interceptor to see what is happening along the route http://camel.apache.org/tracer.html http://camel.apache.org/tracer.html Third, the code you have appended is incomplete since there is insufficient information on the aggregation strategy and what it is doing to the message and what kind of exchange is expected to be returned. For ideas on how to craft what you are looking to do, I am appending a couple of examples that will help you sort things out. https://svn.apache.org/viewvc/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/SplitterTest.java?view=markup https://svn.apache.org/viewvc/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/SplitterTest.java?view=markup https://svn.apache.org/viewvc/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/SpringSplitterStopOnExceptionTest.xml?view=markup https://svn.apache.org/viewvc/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/SpringSplitterStopOnExceptionTest.xml?view=markup Cheers, Ashwin... ------------------- Exchange exchange = this.producerTemplate.send(this.endpoint, ExchangePattern.InOut, new Processor() { @Override public void process(Exchange exchange) throws Exception { /* exchange.setIn(message); */ exchange.getIn().setBody(message); } }); -------------------- ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com Blog: http://opensourceknowledge.blogspot.com --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/Having-trouble-with-an-InOut-route-tp4555130p4555229.html Sent from the Camel - Users mailing list archive at Nabble.com.
