2014-12-11 07:17:29 -05:00
|
|
|
# Mapping JMS Concepts to the Core API
|
2014-12-04 10:25:29 -05:00
|
|
|
|
2015-04-27 17:32:30 -04:00
|
|
|
This chapter describes how JMS destinations are mapped to Apache ActiveMQ Artemis
|
2014-12-04 10:25:29 -05:00
|
|
|
addresses.
|
|
|
|
|
|
2015-04-27 17:32:30 -04:00
|
|
|
Apache ActiveMQ Artemis core is JMS-agnostic. It does not have any concept of a JMS
|
2017-03-09 11:59:09 -05:00
|
|
|
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.
|
2014-12-04 10:25:29 -05:00
|
|
|
|
2017-03-09 11:59:09 -05:00
|
|
|
Likewise, a JMS queue is implemented as an address with name=(the JMS queue name) with an ANYCAST routing type assocatied
|
|
|
|
|
with it.
|
2014-12-04 10:25:29 -05:00
|
|
|
|
2017-03-09 11:59:09 -05:00
|
|
|
Note. That whilst 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.
|
