Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 7 Sep 2014 20:08:29 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12724246.1403910670000.13867.1410120509092@Atlassian.JIRA>
In-Reply-To: <JIRA.12724246.1403910670000@Atlassian.JIRA>
References: <JIRA.12724246.1403910670000@Atlassian.JIRA>
 <JIRA.12724246.1403910670661@arcas>
Subject: [jira] [Commented] (CAMEL-7552) RabbitMQ Component: property to
 allow declare or not queue and exchange.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF GitHub Bot commented on CAMEL-7552:
---------------------------------------

Github user neoramon closed the pull request at:

    https://github.com/apache/camel/pull/201


> RabbitMQ Component: property to allow declare or not queue and exchange.
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-7552
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7552
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-rabbitmq
>    Affects Versions: 2.13.1
>            Reporter: Ramon Rosa da Silva
>            Assignee: Willem Jiang
>              Labels: Camel
>             Fix For: 2.14.0
>
>
> Sometimes to consume a message from RabbitMQ the consumer doesn't konw its  exchange.
> And to send message to exchange, it isn't necessary set queue name, because  the destination queue is defined from a routingkey, but in camel-rabbitmq when queue is blank, is generated a random uuid, and this uuid is used to declare and bind with the exchange. 
> I suggest that the "getEndpoint().declareExchangeAndQueue(chanel)" in Consumer and Producer can be optional. 
> Like:
> boolean declare = true;


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)