[
https://issues.apache.org/jira/browse/QPID-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy resolved QPID-7771.
------------------------------
Resolution: Fixed
The changes were reviewed as part of pair programming by Keith and me
> 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
> Assignee: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
> Attachments:
> 0001-QPID-7771-Java-Broker-Add-support-for-x-replacement-.patch
>
>
> 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.
> For completeness {{ replacement-routing-key}} should be respected if
> presented for routing by an alternate binding.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
