GitHub user w4tson opened a pull request:
https://github.com/apache/camel/pull/1425
CAMEL-10759 RabbitMQ Component binding args
Introduced 3 new Endpoint URI properties
- exchangeArgs
- queueArgs
- bindingArgs
As an easier way to specifiy rabbitmq properties at declare time.
Meanwhile deprecated the ArgsConfigurer class whilst maintaining backwards
compatibility. It's actually possible to use both styles of arg declaration
because the Maps are combined.
Introduced a new integration test for the bindingArgs which tests a headers
exchange correctly routing to a queue. Updated the previous integration test
RabbitMQInOutIntTest to use the new style of arg when setting the "x-expires"
property on the queue.
Finally added a small example of how to declare a headers exchange using
new feature.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/w4tson/camel camel-10759-rabbitmq-binding-args
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1425.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 #1425
----
commit 663e93414e0ba3cee97a17442e3eaae633e0815b
Author: Paul Watson <paul.wat...@pdwtech.com>
Date: 2017-01-29T22:55:52Z
CAMEL-10759 RabbitMQ Component binding args
Introduced 3 new Endpoint URI properties
- exchangeArgs
- queueArgs
- bindingArgs
As an easier way to specifiy rabbitmq properties at declare time.
Meanwhile deprecated the ArgsConfigurer class whilst maintaining backwards
compatibility. It's actually possible to use both styles of arg declaration
because the Maps are combined.
Introduced a new integration test for the bindingArgs which tests a headers
exchange correctly routing to a queue. Updated the previous integration test
RabbitMQInOutIntTest to use the new style of arg when setting the "x-expires"
property on the queue.
Finally added a small example of how to declare a headers exchange using
new feature.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
