| <!DOCTYPE html> |
| <html lang="en"> |
| <head> |
| <meta charset="UTF-8"> |
| <meta http-equiv="X-UA-Compatible" content="IE=edge"> |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| <meta name="generator" content="Asciidoctor 2.0.18"> |
| <link rel="icon" type="image/png" href="images/favicon.png"> |
| <title>Mapping JMS Concepts to the Core API</title> |
| <link rel="stylesheet" href="css/asciidoctor.css"> |
| <link rel="stylesheet" href="css/font-awesome.css"> |
| </head> |
| <body class="book"> |
| <div id="header"> |
| <h1>Mapping JMS Concepts to the Core API</h1> |
| </div> |
| <div id="content"> |
| <div id="preamble"> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>This chapter describes how JMS destinations are mapped to Apache ActiveMQ Artemis addresses.</p> |
| </div> |
| <div class="paragraph"> |
| <p>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.</p> |
| </div> |
| <div class="paragraph"> |
| <p>Likewise, a JMS queue is implemented as an address with name=(the JMS queue name) with an ANYCAST routing type associated with it.</p> |
| </div> |
| <div class="admonitionblock note"> |
| <table> |
| <tr> |
| <td class="icon"> |
| <i class="fa icon-note" title="Note"></i> |
| </td> |
| <td class="content"> |
| 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. |
| </td> |
| </tr> |
| </table> |
| </div> |
| </div> |
| </div> |
| </div> |
| </body> |
| </html> |
