DOC-3707 more attributes (#19)

* more attributes

* fix xref

Author: aimurphy

antora.yml

@@ -8,10 +8,18 @@ nav:
 
 asciidoc:
   attributes:
-    jms_repo: 'https://github.com/datastax/pulsar-jms/'
+    jms_repo: 'https://github.com/datastax/pulsar-jms'
+    astra-streaming-examples-repo: 'https://github.com/datastax/astra-streaming-examples'
+    astra: 'Astra'
     pulsar-reg: 'Apache Pulsar(TM)'
     pulsar: 'Apache Pulsar'
     pulsar-short: 'Pulsar'
     product: 'Starlight for JMS'
     luna-streaming: 'Luna Streaming'
-    astra-streaming: 'Astra Streaming'
+    astra-stream: 'Astra Streaming'
+    activemq-reg: 'Apache ActiveMQ(R)'
+    activemq-short: 'ActiveMQ'
+    tomee-reg: 'Apache TomEE(TM)'
+    maven-reg: 'Apache Maven(TM)'
+    maven-short: 'Maven'
+    kafka-reg: 'Apache Kafka(R)'

modules/ROOT/pages/pulsar-jms-faq.adoc

@@ -46,9 +46,9 @@ IMPORTANT: Globally unique subscription names aren't supported so the correspond
 
 We've provided the following integration examples:
 
-* {jms_repo}blob/master/examples/spring[Spring Boot(R)]
-* {jms_repo}blob/master/examples/payara-micro[Payara Micro(R)]
-* {jms_repo}blob/master/resource-adapter-tests[Apache TomEE(R)]
+* {jms_repo}/blob/master/examples/spring[Spring Boot(R)]
+* {jms_repo}/blob/master/examples/payara-micro[Payara Micro(R)]
+* {jms_repo}/blob/master/resource-adapter-tests[{tomee-reg}]
 
 == How can I build {product} from source?
 
@@ -61,7 +61,7 @@ If you'd like to fork or contribute to {product}:
 git clone git@github.com:datastax/pulsar-jms.git
 ----
 
-. Build using Maven:
+. Build using {maven-short}:
 +
 [source,bash]
 ----

modules/ROOT/partials/jms-quickstart-create-project.adoc

@@ -1,4 +1,4 @@
-. Create a new Maven project:
+. Create a new {maven-short} project:
 +
 [source,bash]
 ----
@@ -19,7 +19,7 @@ cd StarlightForJMSClient
 . Open the project in your IDE, and then add the {product} dependency to the `pom.xml` file.
 +
 This quickstart uses the `pulsar-jms-all` package, which is a fat JAR file that includes all dependencies.
-{company} recommends using the {jms_repo}releases[latest stable release].
+{company} recommends using the {jms_repo}/releases[latest stable release].
 +
 .pom.xml
 [source,xml]
@@ -46,7 +46,7 @@ This quickstart uses the `pulsar-jms-all` package, which is a fat JAR file that
 
 . For this quickstart, include the following plugin configuration in the `build` section:
 +
-* **`<artifactId>maven-assembly-plugin</artifactId>`**: The Maven Assembly Plugin that is used to compile a JAR file with all dependencies included.
+* **`<artifactId>maven-assembly-plugin</artifactId>`**: The {maven-short} Assembly Plugin that is used to compile a JAR file with all dependencies included.
 * **`<descriptorRef>jar-with-dependencies</descriptorRef>`**: An additional descriptor appended to the compiled JAR file name.
 * **`<mainClass>org.example.App</mainClass>`**: The default package and class so you can run the compiled JAR file without any additional specifications.
 +
@@ -72,7 +72,7 @@ This quickstart uses the `pulsar-jms-all` package, which is a fat JAR file that
   </build>
 ----
 
-. In your Maven project, create an `example` subdirectory at `/src/main/java/org`:
+. In your {maven-short} project, create an `example` subdirectory at `/src/main/java/org`:
 +
 [source,bash]
 ----

modules/examples/pages/pulsar-jms-implementation.adoc

@@ -133,8 +133,8 @@ Both of those features can be emulated on the client side with the following lim
 * For shared subscriptions, especially on queues, the message is discarded on the client and is "negative acknowledged" in order to let other consumers receive the message.
 * For `QueueBrowsers`, the message is discarded on the client side.
 
-Currently, the implementation of message selectors is based on Apache ActiveMQ(R) Java client classes, which are imported as a dependency in {product}.
-Apache ActiveMQ is licensed under Apache 2.0.
+Currently, the implementation of message selectors is based on {activemq-reg} Java client classes, which are imported as a dependency in {product}.
+{activemq-short} is licensed under Apache 2.0.
 
 [#subscription-creation]
 == Subscription creation

modules/examples/pages/pulsar-jms-server-side-filters.adoc

@@ -37,11 +37,11 @@ Batch messages with compression consume a non-negligible amount of CPU, heap, an
 This doesn't apply to compressed single messages.
 
 * *Unsupported message types*: {product} doesn't support encrypted batch messages because the filter can't decode the payload of the entry.
-For the same reason, {product} doesn't support custom formats like native Kafka messages.
+For the same reason, {product} doesn't support custom formats like native {kafka-reg} messages.
 
 == Enable server-side filtering
 
-The `.nar` file filter is packaged with {luna-streaming} *2.10.03+* and also available in the GitHub repo https://github.com/datastax/pulsar-jms/releases[here].
+The `.nar` file filter is packaged with {luna-streaming} *2.10.03+* and also available in the GitHub repo {jms_repo}/releases[here].
 
 . Install {product} with the fat JAR that includes all dependencies.
 Put the `.nar` file in `/pulsar/filters`.

modules/jms-migration/pages/pulsar-jms-install.adoc

@@ -30,11 +30,11 @@ However, certain features and compatibility issues that require a specific versi
 
 [tabs]
 ======
-{astra-streaming}::
+{astra-stream}::
 +
 --
-The {pulsar-short} version is managed by Astra.
-Typically, the latest {product} version is compatible with the {pulsar-short} version used by {astra-streaming}.
+The {pulsar-short} version is managed by {astra}.
+Typically, the latest {product} version is compatible with the {pulsar-short} version used by {astra-stream}.
 --
 
 {luna-streaming}::

modules/jms-migration/pages/pulsar-jms-quickstart-sa.adoc

@@ -11,13 +11,13 @@ This quickstart explains how to prepare an {pulsar-reg} streaming instance, and
 
 [tabs]
 ======
-{astra-streaming}::
+{astra-stream}::
 +
 --
-To use {product} with an {astra-streaming} {pulsar-short} cluster, you need the following:
+To use {product} with an {astra-stream} {pulsar-short} cluster, you need the following:
 
-* An active {astra-streaming} {pulsar-short} cluster with a tenant, namespace, and topic that you want to use with {product}.
-If you don't have these structures configured in {astra-streaming}, see the xref:astra-streaming:getting-started:index.adoc[].
+* An active {astra-stream} {pulsar-short} cluster with a tenant, namespace, and topic that you want to use with {product}.
+If you don't have these structures configured in {astra-stream}, see the xref:astra-streaming:getting-started:index.adoc[].
 
 * The connection details for your tenant, which are found on the tenant's **Connect** tab under **Tenant Details**:
 +
@@ -91,23 +91,23 @@ Starting the Docker container produces many status messages and output similar t
 
 == Produce and consume messages with {product}
 
-This example shows how to produce and consume messages with Starlight for JMS using a JMS client, https://openjdk.java.net/install/[Java OpenJDK] 8 or 11, and https://maven.apache.org/install.html[Apache Maven].
+This example shows how to produce and consume messages with Starlight for JMS using a JMS client, https://openjdk.java.net/install/[Java OpenJDK] 8 or 11, and https://maven.apache.org/install.html[{maven-reg}].
 You can also use Gradle with some modifications.
 
-For the complete source code for this example, see the https://github.com/datastax/astra-streaming-examples/tree/master/java/starlight-for-jms[{company} streaming examples repository].
-This example was written for {astra-streaming} but it can be used with {luna-streaming} or self-managed {pulsar-short} clusters by setting the connection properties appropriately.
+For the complete source code for this example, see the {astra-streaming-examples-repo}/tree/master/java/starlight-for-jms[{company} streaming examples repository].
+This example was written for {astra-stream} but it can be used with {luna-streaming} or self-managed {pulsar-short} clusters by setting the connection properties appropriately.
 
 [tabs]
 ======
-{astra-streaming}::
+{astra-stream}::
 +
 --
 include::ROOT:partial$jms-quickstart-create-project.adoc[]
 
 . In the `example` directory, create an `App.java` file.
 In the next steps, you will add code to this file to create a complete program that produces and consumes messages.
 
-. Paste the following code in the file, and then replace the placeholders with the <<prepare-your-pulsar-cluster,tenant connection details, namespace, and topic from {astra-streaming}>>.
+. Paste the following code in the file, and then replace the placeholders with the <<prepare-your-pulsar-cluster,tenant connection details, namespace, and topic from {astra-stream}>>.
 Your editor will report errors because this isn't a complete program yet.
 +
 ./src/main/java/org/example/App.java
@@ -195,9 +195,9 @@ Sending: Hello there!
 Received: Hello there!
 ----
 
-. In {astra-streaming}, go to your tenant's **Namespaces and Topics** tab to inspect the activity in the namespace that you used in the Java program.
+. In {astra-stream}, go to your tenant's **Namespaces and Topics** tab to inspect the activity in the namespace that you used in the Java program.
 +
-If you everything was configured correctly, then the namespace's metrics should reflect that at least one message was published and consumed by your {astra-streaming} {pulsar-short} topic.
+If you everything was configured correctly, then the namespace's metrics should reflect that at least one message was published and consumed by your {astra-stream} {pulsar-short} topic.
 --
 
 {luna-streaming}::
@@ -279,7 +279,7 @@ For more information about consumers, see xref:reference:pulsar-jms-mappings.ado
 mvn clean install
 ----
 +
-The first time you compile the JAR file, Maven downloads all required dependencies.
+The first time you compile the JAR file, {maven-short} downloads all required dependencies.
 Subsequent runs are faster.
 
 . Run the sample application:
@@ -408,7 +408,7 @@ For more information about consumers, see xref:reference:pulsar-jms-mappings.ado
 mvn clean install
 ----
 +
-The first time you compile the JAR file, Maven downloads all required dependencies.
+The first time you compile the JAR file, {maven-short} downloads all required dependencies.
 Subsequent runs are faster.
 
 . Run the sample application:

modules/reference/pages/pulsar-jms-mappings.adoc

@@ -459,7 +459,7 @@ The special `JMSXGroupID` property is defined in the JMS specs as a way to group
 
 {product} maps that property to the message key in {pulsar-short}, ensuring that `JMSXGroupID` is used as the routing key.
 
-This is the same behavior implemented in https://activemq.apache.org/message-groups[Apache ActiveMQ].
+This is the same behavior implemented in https://activemq.apache.org/message-groups[{activemq-reg}].
 
 == See also
 

modules/reference/pages/pulsar-jms-reference.adoc

@@ -86,7 +86,7 @@ Other entries are ignored.
 | String
 | If not specified, for {pulsar-short} standalone instances running on localhost, defaults to the same value as `webServiceUrl`, \`http://localhost:8080`. Can also be specified as \`pulsar://localhost:6650` for {pulsar-short} standalone instances on localhost.
 a| The URL to connect to the {pulsar-short} broker or proxy
-The `brokerServiceUrl` must be specified for {astra-streaming}. Must be customized as required for {pulsar-short} standalone instances that aren't running on localhost.
+The `brokerServiceUrl` must be specified for {astra-stream}. Must be customized as required for {pulsar-short} standalone instances that aren't running on localhost.
 
 | `consumerConfig`
 | no