Exception handling versus normal

[Sven Bauhan <sv...@ast.dfs.de>]

Hi,

have a camel route to receive and decode incoming messages.
Sometimes it can happen the external application on destination endpoint 
is not available. Then I get an exception which I can catch and send 
back an error message.
If the received message is delivered correctly to the endpoint an 
acknowledge message shall be send back.

So my problem is, how I can detect within the route, that the message is 
delivered to the endpoint. I heard about the InOut message concept, but 
I did not understand it yet. Would it be the solution to my problem?
Is there an example how InOut messages can be used?

Thanks Sven

Re: Exception handling versus normal

[Alexander Lomov <al...@me.com>]

Hi Sven,
Let's make things clear from the start.
Your route receives some messages, transforms it and sends to a destination
endpoint.
What's the transport your route uses as a start (from()) endpoint?
What's the transport your route uses to invoke the external system? Once
it's some sort of a synchronous transport like HTTP then just set the
ExchangePattren.InOut for the "to()" node. It makes the endpoint return a
response to your route. Then you can form a response for the system that
invoked you route using 'transform' or 'process' node for example. 




--
View this message in context: http://camel.465427.n5.nabble.com/Exception-handling-versus-normal-tp5751241p5751264.html
Sent from the Camel - Users mailing list archive at Nabble.com.