[QPID-7771] Allow exchange to exchange bindings to substitute the routing key

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: qpid-java-broker-7.0.0
• Component/s: Broker-J
• Assignee: Keith Wall
• Reporter: Keith Wall
• Created: 09/May/17 07:58
• Updated: 02/Oct/19 19:22
• Resolved: 13/Sep/17 13:09

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.

For completeness {{ replacement-routing-key}} should be respected if presented for routing by an alternate binding.