mirror of
https://github.com/apache/activemq-artemis.git
synced 2025-02-08 02:59:14 +00:00
2b5d8f3b80
- Split protocols into individual chapters - Reorganize summary to flow more logically - Fill in missing parameters in configuration index - Normalize spaces for ordered and unordered lists - Re-wrap lots of text for readability - Fix incorrect XML snippets - Normalize table formatting - Improve internal links with anchors - Update content to reflect new address model - Resized architecture images to avoid excessive white-space - Update some JavaDoc - Update some schema elements - Disambiguate AIO & ASYNCIO where necessary - Use URIs instead of Objects in code examples
15 lines
726 B
Markdown
15 lines
726 B
Markdown
# Mapping JMS Concepts to the Core API
|
|
|
|
This chapter describes how JMS destinations are mapped to Apache ActiveMQ
|
|
Artemis addresses.
|
|
|
|
Apache ActiveMQ Artemis core is JMS-agnostic. It does not have any concept of a
|
|
JMS topic. A JMS topic is implemented in core as an address with name=(the
|
|
topic name) and with a MULTICAST routing type with zero or more queues bound to
|
|
it. Each queue bound to that address represents a topic subscription.
|
|
|
|
Likewise, a JMS queue is implemented as an address with name=(the JMS queue
|
|
name) with an ANYCAST routing type associated with it.
|
|
|
|
**Note:** While it is possible to configure a JMS topic and queue with the same
|
|
name, it is not a recommended configuration for use with cross protocol. |