Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

ARTEMIS-1883 clarify docs for use of '::'

This commit is contained in:
Justin Bertram 2021-06-07 13:45:01 -05:00 committed by GitHub
parent 3913c17c8d
commit a38f0092f2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/user-manual/en/address-model.md
View File

@ -353,10 +353,15 @@ queues. The broker decides on behalf of the client which queues to send
messages to or from which queue to receive messages. However, more advanced use messages to or from which queue to receive messages. However, more advanced use
cases might require that the client specify a queue directly. In these cases might require that the client specify a queue directly. In these
situations the client uses a fully qualified queue name, by specifying both situations the client uses a fully qualified queue name, by specifying both
the address name and the queue name, separated by a ::. the address name and the queue name, separated by `::`.
> **Note**
>
> The string `::` should only be used for FQQN and not in any other context
> in address or queue names.
Currently Artemis supports fully qualified queue names on Core, AMQP, JMS, Currently Artemis supports fully qualified queue names on Core, AMQP, JMS,
OpenWire, MQTT and STOMP protocols for receiving messages only. OpenWire, MQTT and STOMP protocols for both sending and receiving messages.
### Specifying a Fully Qualified Queue Name ### Specifying a Fully Qualified Queue Name