On Tue, May 8, 2012 at 9:19 PM, barry_allen <coldgint...@gmail.com> wrote: > Ok, thank you both very much, I got it. I needed to use inOnly tags on the > route as sekaijin mentioned. I was using <to ...> tags (which apparently > allowed those steps to return output into the mina route), and simply > changed them to <inOnly ... /> tags. What this does is not let any output > from those steps of the route re-enter the mina route. The original message > was then left intact after those steps, and at the bottom of my try block I > was able to build the ack (and the nak within the catch). > > Thank you once again Claus and sekaijin, I really appreciate it. > > ps - Just for clarity, I didn't need to wiretap anything in the route > related to the ack/nak. >
Yeah I would assume the <inOnly> is to a JMS queue or some sort like that? btw we prefer to use <to pattern="InOnly" uri="xxx"/> over <inOnly> > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-to-send-ack-and-then-resume-route-with-original-message-tp5692336p5695682.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
