On Tue, May 8, 2012 at 2:18 PM, barry_allen <coldgint...@gmail.com> wrote: > Thanks for responding, Claus. Just a little clarification on wiretap: > > 1.) If I wiretap in this fashion, and I set getIn().body(ack) on the wiretap > thread from the mina route, will the ack be able to find it's way back to > the server (that set the original message) correctly, as with the wiretap I > am now on a different thread than the original tcp socket (if my > understanding of wiretap is correct)? > > 2.) I am using spring tags. If I wiretap, since I need to make a call into a > bean that will both build the ack message for me and send the ack back to > the server by setting it on the exchange getIn().body(), is the following > correct for resuming on the main route with the original message? > > <from ref="my-mina-tcp-in"> > <wireTap uri="direct:sendTcpAck" processorRef="myAckCreatorAndSenderBean"/> > <from ref="direct:sendTcpAck"> > (ack is sent and original message from my-mina-tcp-in is now present for > processing here) > ...
You can build the ACK response *after* the wire tap. from wire Tap bean (that creates ACK) > > Thank you once again. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-to-send-ack-and-then-resume-route-with-original-message-tp5692336p5693873.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/
