Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 13 Nov 2015 15:25:11 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12771617.1422821690000.62582.1447428311104@Atlassian.JIRA>
In-Reply-To: <JIRA.12771617.1422821690000@Atlassian.JIRA>
References: <JIRA.12771617.1422821690000@Atlassian.JIRA>
 <JIRA.12771617.1422821690680@arcas>
Subject: [jira] [Commented] (CAMEL-8302) Rabbitmq shouldn't require/bind
 queue if not specified
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004111#comment-15004111 ] 

Claus Ibsen commented on CAMEL-8302:
------------------------------------

Thanks can you log a new PR and rebase from master first as the code has been merged already.

> 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
>            Assignee: Claus Ibsen
>             Fix For: 2.16.1, 2.17.0
>
>
> 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)