[
https://issues.apache.org/jira/browse/CAMEL-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000926#comment-15000926
]
David Williams edited comment on CAMEL-8302 at 11/11/15 7:22 PM:
-----------------------------------------------------------------
I have created a PR implementing the logic suggested in the original
description. I took this approach rather than the one suggested above (setting
the queue to null) to avoid backwards compatibility issues for those who may be
relying on the random integer queues.
https://github.com/apache/camel/pull/676
was (Author: david-gathering):
I have created a PR implementing the logic suggested in the original
description. I took this approach rather than the one suggested above (setting
the queue to null) to avoid backwards compatibility issues for those who may be
relying on the random integer queues.
> Rabbitmq shouldn't require/bind queue if not specified
> -------------------------------------------------------
>
> Key: CAMEL-8302
> URL: https://issues.apache.org/jira/browse/CAMEL-8302
> Project: Camel
> Issue Type: Bug
> Components: camel-rabbitmq
> Affects Versions: 2.14.1
> Reporter: Sajjad Akhter
> Fix For: Future
>
>
> Current implementation is declaring both exchange and queue on any init
> (producer or consumer). In case of producer one don't need queue and may not
> know who going to be client.
> We can add flag skipQueueDeclare so that it won't genrate uuid queue.
> i can provide PR if it helps.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
