From e04f3214cb6697c98ac6009f9f39b240ff811fb1 Mon Sep 17 00:00:00 2001 From: Robbie Gemmell Date: Wed, 1 Dec 2021 12:07:05 +0000 Subject: [PATCH] NO-JIRA: update source file to ensure apache/activemq-website#68 remains resolved for future site refreshes --- docs/migration-guide/en/destinations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/migration-guide/en/destinations.md b/docs/migration-guide/en/destinations.md index 5753c2846e..667b002d6b 100644 --- a/docs/migration-guide/en/destinations.md +++ b/docs/migration-guide/en/destinations.md @@ -12,7 +12,7 @@ In ActiveMQ, destinations are pre-defined in the `` section of the ``` -Things looks a bit different in Artemis. We already explained that queues are `anycast` addresses and topics are `muticast` ones. We're not gonna go deep into the address settings details here and you're advised to look at the user manual for that. Let's just see what we need to do in order to replicate ActiveMQ configuration. +Things looks a bit different in Artemis. We already explained that queues are `anycast` addresses and topics are `multicast` ones. We're not gonna go deep into the address settings details here and you're advised to look at the user manual for that. Let's just see what we need to do in order to replicate ActiveMQ configuration. Addresses are defined in `` section of the `etc/broker.xml` configuration file. So the corresponding Artemis configuration for the ActiveMQ example above, looks like this: