camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ashwin Karpe <>
Subject Re: Camel Exchange Patters
Date Sun, 12 Sep 2010 14:27:05 GMT


My 2 cents worth on this topic.

The exchange patterns in Camel are originally defined in the W3C WSDL 2.0

>From a camel perspective, the Robust In-Only is of limited applicability
since the consumer endpoint is expected to send an acknowledgement but the
processing is still In-Only. Internal to the route a RobustIn-only has no
meaning since the response is sent by the last route endpoint directly to
the consumer and does not go back through the processors encountered on the

In-Optional out is more nuanced and again needs to be something that affects
the producer endpoint (client) and consumer endpoint (service) since both
have to be able to properly address the handshake. Moreover connection
timeouts and the window in which a response may be received needs to
addressed. Internal to the route it is no different than the In-Out. 

Hence internal to the route In-Only and In-Out exchanges are sufficient
address all possibilities with the exchange pattern specifying a flag that
provides more context to the consumer and producer endpoints when a message
leaves or enters a camel route.

Hope this helps.



Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary) 

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message