This is an automated email from the ASF dual-hosted git repository.
clebertsuconic 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 a008c0e ARTEMIS-3257 fixed documentation issue wrt federation
configuration
a008c0e is described below
commit a008c0ecc9a90f17a71cc5578714b98c38026140
Author: Erwin Dondorp <[email protected]>
AuthorDate: Tue Apr 20 02:32:00 2021 +0200
ARTEMIS-3257 fixed documentation issue wrt federation configuration
---
docs/user-manual/en/federation-address.md | 6 +++---
docs/user-manual/en/federation-queue.md | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/user-manual/en/federation-address.md
b/docs/user-manual/en/federation-address.md
index 60e6793..c377d06 100644
--- a/docs/user-manual/en/federation-address.md
+++ b/docs/user-manual/en/federation-address.md
@@ -257,7 +257,7 @@ as a hub and spoke topology
All of the same configuration options apply to `downstream` as does `upstream`
with the exception of one
extra configuration flag that needs to be set:
- The `transport-connector-ref` is an element pointing to a
+ The `upstream-connector-ref` is an element pointing to a
`connector` elements defined elsewhere. This ref is used to tell the
downstream broker
what connector to use to create a new upstream connection back to the
downstream broker.
@@ -290,14 +290,14 @@ Sample Downstream Address Federation setup:
<static-connectors>
<connector-ref>eu-east-connector1</connector-ref>
</static-connectors>
- <transport-connector-ref>netty-connector</transport-connector-ref>
+ <upstream-connector-ref>netty-connector</upstream-connector-ref>
<policy ref="news-address-federation"/>
</downstream>
<downstream name="eu-west-1" >
<static-connectors>
<connector-ref>eu-west-connector1</connector-ref>
</static-connectors>
- <transport-connector-ref>netty-connector</transport-connector-ref>
+ <upstream-connector-ref>netty-connector</upstream-connector-ref>
<policy ref="news-address-federation"/>
</downstream>
diff --git a/docs/user-manual/en/federation-queue.md
b/docs/user-manual/en/federation-queue.md
index bbceaae..76f5ac9 100644
--- a/docs/user-manual/en/federation-queue.md
+++ b/docs/user-manual/en/federation-queue.md
@@ -223,7 +223,7 @@ as a hub and spoke topology.
All of the same configuration options apply to `downstream` as does `upstream`
with the exception of one
extra configuration flag that needs to be set:
- The `transport-connector-ref` is an element pointing to a
+ The `upstream-connector-ref` is an element pointing to a
`connector` elements defined elsewhere. This ref is used to tell the
downstream broker
what connector to use to create a new upstream connection back to the
downstream broker.
@@ -257,14 +257,14 @@ extra configuration flag that needs to be set:
<static-connectors>
<connector-ref>eu-east-connector1</connector-ref>
</static-connectors>
- <transport-connector-ref>netty-connector</transport-connector-ref>
+ <upstream-connector-ref>netty-connector</upstream-connector-ref>
<policy ref="news-address-federation"/>
</downstream>
<downstream name="eu-west-1" >
<static-connectors>
<connector-ref>eu-west-connector1</connector-ref>
</static-connectors>
- <transport-connector-ref>netty-connector</transport-connector-ref>
+ <upstream-connector-ref>netty-connector</upstream-connector-ref>
<policy ref="news-address-federation"/>
</downstream>
