Hi everyone,
I'm developing an application that relies mostly on Camel (3.9.0) and its
dedicated RabbitMQ / REST components.
My routes are specified in XML (with Spring beans).
Here's a simple route :
<camel:rest path="/percolate">
<camel:post>
<camel:route>
<camel:log message="in :: percolate" logName="app.log" />
<camel:inOut uri="rabbitmq:percolate?queue=percolate_queue"/>
</camel:route>
</camel:post>
</camel:rest>
The percolate_queue defined in another XML contains a single Camel processor,
which returns a basic JSON.
When I'm calling the REST endpoint :
* A message is sent to percolate_queue without issues
* The Camel processor is invoked, and returns its value (which I get as a
response for my REST call)
However, I noticed a temporary queue amq.gen.XXX has been created
automatically, to handle the reply.
Is it the standard behaviour ?
Before using camel-rabbitmq, we were relying on camel-spring-amqp
(https://github.com/Bluelock/camel-spring-amqp), which is now obsolete (and
triggered the switch to camel-rabbitmq).
And with this component, we did not have any temporary queues for this kind of
routes.
May it be because the replyTo property (CamelRabbitmqReplyTo) is not set ?
If so, how can I set/adjust it to point on the existing percolate_queue ?
Thanks a lot for your answers.
Best regards,
Guillaume.
