Merge pull request #2 from datastax/redirects

mendonk · web-flow · commit c5196ffb52d2 · 2022-11-18T14:24:00.000-05:00
redirects
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
@@ -1,6 +1,7 @@
 = About {starlight_jms}
 
 :page-tag: starlight-jms,planner,dev,admin,pulsar,jms
+:page-alias: docs@starlight-for-jms::index.adoc,
 
 {starlight_jms} is the first highly compliant JMS implementation designed to run on a modern streaming platform. It allows enterprises to take advantage of the scalability and resiliency of a modern streaming platform to run their existing JMS applications. Because Apache Pulsar™ is open-source and cloud-native, {starlight_jms} enables enterprises to move their JMS applications to run on-premises and in any cloud environment.
 
diff --git a/modules/examples/pages/pulsar-jms-batch-ack.adoc b/modules/examples/pages/pulsar-jms-batch-ack.adoc
@@ -1,4 +1,5 @@
 = Batch index acknowledgement
+:page-alias: docs@starlight-for-jms::pulsar-jms-batch-ack.adoc
 
 {starlight_jms} version {product_version} improves acknowledgement of batched messages by supporting the tracking of 'ack' status by *batch index*. +
 
diff --git a/modules/examples/pages/pulsar-jms-implementation.adoc b/modules/examples/pages/pulsar-jms-implementation.adoc
@@ -1,6 +1,7 @@
 = {starlight_jms} implementation details
 
 :page-tag: starlight-jms,dev,pulsar,jms
+:page-alias: docs@starlight-for-jms::pulsar-jms-implementation.adoc
 
 A discussion of design and implementation decisions made to support JMS requirements.
 
diff --git a/modules/examples/pages/pulsar-jms-server-side-filters.adoc b/modules/examples/pages/pulsar-jms-server-side-filters.adoc
@@ -1,4 +1,5 @@
 = Enabling server-side filters
+:page-alias: docs@starlight-for-jms::pulsar-jms-server-side-filters.adoc
 
 {starlight_jms} version {product_version} offers *server-side filtering*, which executes JMS filtering features on the Pulsar Broker instead of the Client. +
 Before {product_version}, filtering was implemented with `jms.enableClientSideEmulation=true` on the Client side, which meant the Client application received all messages, even if they didn't match the filter. This caused inefficient network, CPU, and memory usage.
diff --git a/modules/jms-migration/pages/pulsar-jms-install.adoc b/modules/jms-migration/pages/pulsar-jms-install.adoc
@@ -1,7 +1,7 @@
 = Installing {starlight_jms} 
 
 :page-tag: starlight-jms,install,dev,admin,pulsar,jms,java,maven
-
+:page-alias: docs@starlight-for-jms::pulsar-jms-install.adoc
 == Compatibility
 
 The current version of {starlight_jms} is {product_version}. Version {product_version} includes:
diff --git a/modules/jms-migration/pages/pulsar-jms-quickstart-astra.adoc b/modules/jms-migration/pages/pulsar-jms-quickstart-astra.adoc
@@ -1,6 +1,7 @@
 = {starlight_jms} Astra Streaming quick start 
 
 :page-tag: starlight-jms,dev,quickstart,pulsar,jms
+:page-alias: docs@starlight-for-jms::pulsar-jms-quickstart-astra.adoc
 
 This quick start will get you up and running with a simple command-line Java JMS client that can talk to an Apache Pulsar™ streaming instance. The client:
 
diff --git a/modules/jms-migration/pages/pulsar-jms-quickstart-sa.adoc b/modules/jms-migration/pages/pulsar-jms-quickstart-sa.adoc
@@ -1,6 +1,7 @@
 = {starlight_jms} standalone quick start 
 
 :page-tag: starlight-jms,dev,quickstart,pulsar,java,jms
+:page-alias: docs@starlight-for-jms::pulsar-jms-quickstart-sa.adoc
 
 This quick start will get you up and running with a simple command-line Java JMS client that can talk to a local Apache Pulsar™ installation. The client:
 
diff --git a/modules/reference/pages/pulsar-jms-mappings.adoc b/modules/reference/pages/pulsar-jms-mappings.adoc
@@ -1,6 +1,7 @@
 = Mapping Pulsar concepts to JMS specifications
 
 :page-tag: starlight-jms,planner,dev,admin,pulsar,jms
+:page-alias: docs@starlight-for-jms::pulsar-jms-mappings.adoc
 
 JMS specifications are built upon the concepts of *Topics* and *Queues*, but Apache Pulsar™ has only a general concept of *Topics* that can model both of those two domains.
 
diff --git a/modules/reference/pages/pulsar-jms-reference.adoc b/modules/reference/pages/pulsar-jms-reference.adoc
@@ -1,6 +1,7 @@
 = {starlight_jms} configuration reference 
 
 :page-tag: starlight-jms,dev,admin,manage,pulsar,jms
+:page-alias: docs@starlight-for-jms::pulsar-jms-reference.adoc
 
 A complete configuration reference for {starlight_jms}. 
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,5 @@`
`1`	`1`	`= Batch index acknowledgement`
	`2`	`+:page-alias: docs@starlight-for-jms::pulsar-jms-batch-ack.adoc`
`2`	`3`
`3`	`4`	`{starlight_jms} version {product_version} improves acknowledgement of batched messages by supporting the tracking of 'ack' status by batch index. +`
`4`	`5`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,5 @@`
`1`	`1`	`= Enabling server-side filters`
	`2`	`+:page-alias: docs@starlight-for-jms::pulsar-jms-server-side-filters.adoc`
`2`	`3`
`3`	`4`	`{starlight_jms} version {product_version} offers server-side filtering, which executes JMS filtering features on the Pulsar Broker instead of the Client. +`
`4`	`5`	Before {product_version}, filtering was implemented with `jms.enableClientSideEmulation=true` on the Client side, which meant the Client application received all messages, even if they didn't match the filter. This caused inefficient network, CPU, and memory usage.