You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2017/06/16 08:31:00 UTC
[jira] [Updated] (QPID-7771) Allow exchange to exchange bindings to
substitute the routing key
[ https://issues.apache.org/jira/browse/QPID-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-7771:
-----------------------------
Description:
QPID-6028 added support for exchange to exchange bindings.
This feature will have utility in aiding the migration of pub/sub
messaging application between the old Qpid JMS AMQP 0-x client and the Qpid JMS Client. It will allow topic publishers and subscribers to be
upgraded to the new client at different times, avoiding a big-bang upgrade and avoiding addressing changes.
For a topic published by a Qpid JMS AMQP 0-x application to amq.topic/foo, an exchange to exchange binding {{amq.topic/foo => foo}} where foo is a fanout instance will allow an application using the Qpid JMS Client to subscribe successfully.
For a topic published by a Qpid JMS Client application to fanout exchange instance foo, and exchange to exchange binding {{foo => amq.topic (arguments: replacement-routing-key=foo)}} will allow an application using the Qpid JMS AMQP 0-x client to successfully subscribe.
was:
QPID-6028 added support for exchange to exchange bindings.
This feature will have utility in aiding the migration of pub/sub
messaging application between the old Qpid JMS AMQP 0-x client and the Qpid JMS Client. It will allow topic publishers and subscribers to be
upgraded to the new client at different times, avoiding a big-bang upgrade and avoiding addressing changes.
For a topic published by a Qpid JMS AMQP 0-x application to amq.topic/foo, an exchange to exchange binding {{amq.topic/foo => foo}} where foo is a fanout instance will allow an application using the Qpid JMS Client to subscribe successfully.
For a topic published by a Qpid JMS Client application to fanout exchange instance foo, and exchange to exchange binding {{foo => amq.topic (arguments: replacement-routing-key=foo)}} will allow an application using the Qpid JMS AMQP 0-x client to successfully subscribe.
QPID-6028 added support for exchange to exchange bindings. The only addition is the support for an special binding argument {{replacement-routing-key}}. If this is present on the binding, it will replace the routing key of the incoming message.
> Allow exchange to exchange bindings to substitute the routing key
> -----------------------------------------------------------------
>
> Key: QPID-7771
> URL: https://issues.apache.org/jira/browse/QPID-7771
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> QPID-6028 added support for exchange to exchange bindings.
> This feature will have utility in aiding the migration of pub/sub
> messaging application between the old Qpid JMS AMQP 0-x client and the Qpid JMS Client. It will allow topic publishers and subscribers to be
> upgraded to the new client at different times, avoiding a big-bang upgrade and avoiding addressing changes.
> For a topic published by a Qpid JMS AMQP 0-x application to amq.topic/foo, an exchange to exchange binding {{amq.topic/foo => foo}} where foo is a fanout instance will allow an application using the Qpid JMS Client to subscribe successfully.
> For a topic published by a Qpid JMS Client application to fanout exchange instance foo, and exchange to exchange binding {{foo => amq.topic (arguments: replacement-routing-key=foo)}} will allow an application using the Qpid JMS AMQP 0-x client to successfully subscribe.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org