Hi, Yeah that's the bit I'm struggling back with I though with the inOut if an exception was thrown / not handled then camel would return something back automatically so that the exchange would say fault and the original route would continue from the inOut.
So I was thinking something like inOut(external_server_to_save).contentRouter( if (failed) -> fail_queue otherwise to(recipt_queue) would have been the sort of flow. But it seems I now need a failed recipt rout. I also thought the pipe / endpoint being used is the same for the request reply, i.e. if I the first server connects with netty to a port on the second server where its listening then camel automatically puts the replies back on that connection / pipe and it resumes at the inOut of the route otherwise I'm not really understanding the point of inOut... brain ache. Hmmm, I need to play / read with this some more and look more into netty and see if I can come up with something. Alot of the apps I work with use protobuf or hand rolled serialisation. Usually the app connects to the server and its a 2 way free for all over the pipe. Thanks again Claus for the help / time. Cheers, Jon -- View this message in context: http://camel.465427.n5.nabble.com/Exception-handling-tp5754013p5754209.html Sent from the Camel - Users mailing list archive at Nabble.com.
