I'd like to implement the request-reply pattern over RabbitMQ the following way: 1. The request is sent to a RabbitMQ fanout exchange (i.e. it will be received by multiple consumers) 2. Each consumer prepares and sends its on response (e.g. if they can fulfill the given request/order and at what cost) 3. The sender route aggregates the responses (e.g. drops responses, where the cost is too high and sorts the remaining ones by cost) 4. Then return this list to the original caller
If I use inOut to send out the request to the fanout exchange, Camel will create a temporary reply queue with a listener and as soon as the first response arrives, it stops listening to further ones and "returns", i.e. it isn't possible to aggregate the responses. How can I combine inOut with aggregator to realize the expected flow? (The only way, I could make it work so far is to use inOnly and set up another route to gather and aggregate the responses. But then I cannot acknowledge the messages at the end of the entire processing.) Cheers Andras -- View this message in context: http://camel.465427.n5.nabble.com/RabbitMQ-fanout-exchange-request-reply-aggergator-tp5796289.html Sent from the Camel - Users mailing list archive at Nabble.com.
