Description
Although the STOMP protocol does not attach any semantics to the destination names, most implementations do.
ActiveMQ 5.x, Apollo and RabbitMQ (at least) use the /queue/ and /topic/ prefixes to identify destinations that should behave like JMS queues and topics. Artemis differs.
To ease interoperability, it would be good to control the destination prefixes used by Artemis.
FWIW, this is what Apollo does. Its STOMP manual contains:
The stomp configuration element can also be used to control how the destination headers are parsed and interpreted. The supported attributes are:
- queue_prefix : Defaults to /queue/
- topic_prefix : Defaults to /topic/
- path_separator : Defaults to .
- destination_separator : Defaults to ,
- any_child_wildcard : Defaults to *
- regex_wildcard_start : Defaults to {
- regex_wildcard_end : Defaults to }
- any_descendant_wildcard : Defaults to **
Attachments
Issue Links
- duplicates
-
ARTEMIS-880 Support address prefixing
-
- Closed
-
- is duplicated by
-
-
- Closed
-