[ENTMQBR-327] Design and implement an addressing system that can be used cross-protocol - JBoss Issue Tracker

XML

Word

Printable

Target Release:

A-MQ 7.0.0.GA
Affects:

Documentation (Ref Guide, User Guide, etc.), Release Notes
Release Notes Text:

Hide
Previously, there were issues observed when sending/receiving messages between a core JMS client and clients using other protocols. This was because the core JMS client used prefixes for destinations (namely, jms.topic. and jms.queue) that were hidden. The new addressing model in AMQ 7 enables customers to configure destinations that independent of JMS conventions.

Show
Previously, there were issues observed when sending/receiving messages between a core JMS client and clients using other protocols. This was because the core JMS client used prefixes for destinations (namely, jms.topic. and jms.queue) that were hidden. The new addressing model in AMQ 7 enables customers to configure destinations that independent of JMS conventions.
Release Notes Docs Status:
Documented as Feature Request

improve the addressing system so we dont have issues with jms prefixes and can define subscriptions for all protocol models. first draft of approach at https://docs.google.com/document/d/1A1iXJ9Jhv3wpnmjj3tB5fOR1eSJIAIGchte0j43Xi2A/edit

causes

ENTMQBR-211 JMS Openwire client is unable to find destinations other than prefixed with "jms.queue."

incorporates

ENTMQBR-61 Can't show details message that not visible ID

is related to

ENTMQ-1959 update and imrove amqp protocol head after changes to addressing

ENTMQBR-342 update HawtIO plugin to deal with addressing updates

relates to

ENTMQBR-211 JMS Openwire client is unable to find destinations other than prefixed with "jms.queue."