Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
activemq-artemis/docs/user-manual/en/jms-core-mapping.md

15 lines
726 B
Markdown
Raw Normal View History

documentation review fixes
2014-12-11 07:17:29 -05:00
# Mapping JMS Concepts to the Core API
ACTIVEMQ6-9 - port to markdown https://issues.apache.org/jira/browse/ACTIVEMQ6-9 remove the jboss jdocbook build and style and replace using plane markdown
2014-12-04 10:25:29 -05:00
ARTEMIS-1912 big doc refactor - 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
2018-03-09 10:07:38 -05:00
This chapter describes how JMS destinations are mapped to Apache ActiveMQ
Artemis addresses.
ACTIVEMQ6-9 - port to markdown https://issues.apache.org/jira/browse/ACTIVEMQ6-9 remove the jboss jdocbook build and style and replace using plane markdown
2014-12-04 10:25:29 -05:00
ARTEMIS-1912 big doc refactor - 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
2018-03-09 10:07:38 -05:00
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.
ACTIVEMQ6-9 - port to markdown https://issues.apache.org/jira/browse/ACTIVEMQ6-9 remove the jboss jdocbook build and style and replace using plane markdown
2014-12-04 10:25:29 -05:00
ARTEMIS-1912 big doc refactor - 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
2018-03-09 10:07:38 -05:00
Likewise, a JMS queue is implemented as an address with name=(the JMS queue
name) with an ANYCAST routing type associated with it.
ACTIVEMQ6-9 - port to markdown https://issues.apache.org/jira/browse/ACTIVEMQ6-9 remove the jboss jdocbook build and style and replace using plane markdown
2014-12-04 10:25:29 -05:00
ARTEMIS-1912 big doc refactor - 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
2018-03-09 10:07:38 -05:00
**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.