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

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

GitHub user FabianChanton opened a pull request:

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

    CAMEL-9815 Add URI parameter to skip declaration of exchange

    As described in 
[CAMEL-9815](https://issues.apache.org/jira/browse/CAMEL-9815) it could be 
helpful to skip the declaration of the exchange (because it exists already). I 
propose this could be done via an URI parameter "skipExchangeDeclare", similar 
to "skipQueueDeclare"

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/FabianChanton/camel master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/928.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #928
    
----
commit eb85ef59e79a43111da9cf373524a37f64167047
Author: Fabian Chanton <[email protected]>
Date:   2016-04-05T09:21:06Z

    CAMEL-9815 Add URI parameter to skip declaration of exchange

----


> Add URI parameter to skip the declaration of the exchange
> ---------------------------------------------------------
>
>                 Key: CAMEL-9815
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9815
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-rabbitmq
>    Affects Versions: 2.17.0
>            Reporter: Fabian Chanton
>            Priority: Minor
>
> Certain servers require to declare a queue on an existing exchange (e.g. the 
> standard exchange without a name).
> These servers don't allow to re declare these existing exchanges.
> In this case it would be helpful to have an option similar to the 
> skipQueueDeclare option.



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

Reply via email to