From a38f0092f239ad2f3f09854bd9e2c1c7c5f1964e Mon Sep 17 00:00:00 2001 From: Justin Bertram Date: Mon, 7 Jun 2021 13:45:01 -0500 Subject: [PATCH] ARTEMIS-1883 clarify docs for use of '::' --- docs/user-manual/en/address-model.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/user-manual/en/address-model.md b/docs/user-manual/en/address-model.md index ce04547c4e..599b871e5a 100644 --- a/docs/user-manual/en/address-model.md +++ b/docs/user-manual/en/address-model.md @@ -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 cases might require that the client specify a queue directly. In these 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, -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