This is an automated email from the ASF dual-hosted git repository.
robbie pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-artemis.git
The following commit(s) were added to refs/heads/main by this push:
new e15bc1b35f NO-JIRA: fix typos/wording in key-differences.md and
authentication.md
e15bc1b35f is described below
commit e15bc1b35fef5553239d28b353c62dc488b3aedf
Author: iamgd67 <6...@gd67.com>
AuthorDate: Sun Jun 25 10:42:17 2023 +0800
NO-JIRA: fix typos/wording in key-differences.md and authentication.md
This closes #4525
---
docs/migration-guide/en/authentication.md | 2 +-
docs/migration-guide/en/key-differences.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/migration-guide/en/authentication.md
b/docs/migration-guide/en/authentication.md
index 474cb07c7a..225d6e68d9 100644
--- a/docs/migration-guide/en/authentication.md
+++ b/docs/migration-guide/en/authentication.md
@@ -21,6 +21,6 @@ In Artemis, the same thing is achieved by defining
`<jaas-security>` configurati
From this point on, you can go and define your users and their roles in
appropriate files, like `conf/users.properties` and `conf/groups.properties` in
ActiveMQ. Similarly, `etc/artemis-users.properties` and
`etc/artemis-roles.properties` files are used in Artemis. These files are
interchangeable, so you should be able to just copy your existing configuration
over to the new broker.
-If your deployment is more complicated that this and requires some advanced
JAAS configuration, you'll need go and change the `etc/login.config` file. It's
important to say that all custom JAAS modules and configuration you were using
in ActiveMQ should be compatible with Artemis.
+If your deployment is more complicated than this and requires some advanced
JAAS configuration, you'll need go and change the `etc/login.config` file. It's
important to say that all custom JAAS modules and configuration you were using
in ActiveMQ should be compatible with Artemis.
Finally, in case you're still using ActiveMQ's *Simple Authentication Plugin*,
which defines users and groups directly in the broker's xml configuration file,
you'll need to migrate to JAAS as Artemis doesn't support the similar concept.
diff --git a/docs/migration-guide/en/key-differences.md
b/docs/migration-guide/en/key-differences.md
index d3791b708d..c3ae057828 100644
--- a/docs/migration-guide/en/key-differences.md
+++ b/docs/migration-guide/en/key-differences.md
@@ -19,7 +19,7 @@ This is one of the main differences between ActiveMQ 5.x and
Artemis. It's impor
## Addressing differences
-Another big difference that's good to cover early on is the difference is how
message addressing and routing is done. ActiveMQ started as an open source JMS
implementation, so at its core all JMS concepts like queues, topics and durable
subscriptions are implemented as the first-class citizens. It's all based on
OpenWire protocol developed within the project and even KahaDB message store is
OpenWire centric. This means that all other supported protocols, like MQTT and
AMQP are translated [...]
+Another big difference that's good to cover early on is the difference of how
message addressing and routing is done. ActiveMQ started as an open source JMS
implementation, so at its core all JMS concepts like queues, topics and durable
subscriptions are implemented as the first-class citizens. It's all based on
OpenWire protocol developed within the project and even KahaDB message store is
OpenWire centric. This means that all other supported protocols, like MQTT and
AMQP are translated [...]
Artemis took a different approach. It implements only queues internally and
all other messaging concepts are achieved by routing messages to appropriate
queue(s) using addresses. Messaging concepts like publish-subscribe (topics)
and point-to-point (queues) are implemented using different type of routing
mechanisms on addresses. *Multicast* routing is used to implement
*publish-subscribe* semantics, where all subscribers to a certain address will
get their own internal queue and messages [...]
