Hello Souciance Thanks for your answer!
The standard case you described works well for me. However the following does not work: I create an endpoint with the following URI: rabbitmq://<host>:<port>/ (leaving the exchange part empty because i need to declare the queue on the default exchange) This causes the following response from the server: reply-text=ACCESS_REFUSED - operation not permitted on the default exchange I guess this is because the RabbitMQ endpoint declares the queue AND exchange, but the default exchange is already present on the server. If I try "declare=false" it doesn't work either because the Endpoint assumes a random queue ID and that queue doesn't exist (because we don't declare it) I saw that there is an option "skipQueueDeclare" which would only declare the exchange but not the queue. What i am looking for is the opposite: declare the queue but not the exchange. Something similar to the exchangeDeclarePassive method of the com.rabbitmq.client.channel class. Best Regards Fabian -- View this message in context: http://camel.465427.n5.nabble.com/RabbitMQ-Declare-queue-on-existing-exchange-tp5778263p5778270.html Sent from the Camel - Users mailing list archive at Nabble.com.
