Skip to content

Commit 65f5268

Browse files
committed
Fix page-aliases
1 parent d68d6b3 commit 65f5268

9 files changed

+9
-9
lines changed

modules/ROOT/pages/index.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
= About {starlight_jms}
22

33
:page-tag: starlight-jms,planner,dev,admin,pulsar,jms
4-
:page-aliases: docs@starlight-for-jms::index.adoc,
4+
:page-aliases: docs@starlight-jms::index.adoc,
55

66
{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.
77

modules/examples/pages/pulsar-jms-batch-ack.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
= Batch index acknowledgement
2-
:page-aliases: docs@starlight-for-jms::pulsar-jms-batch-ack.adoc
2+
:page-aliases: docs@starlight-jms::pulsar-jms-batch-ack.adoc
33

44
{starlight_jms} version {product_version} improves acknowledgement of batched messages by supporting the tracking of 'ack' status by *batch index*. +
55

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
= {starlight_jms} implementation details
22

33
:page-tag: starlight-jms,dev,pulsar,jms
4-
:page-aliases: docs@starlight-for-jms::pulsar-jms-implementation.adoc
4+
:page-aliases: docs@starlight-jms::pulsar-jms-implementation.adoc
55

66
A discussion of design and implementation decisions made to support JMS requirements.
77

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
= Enabling server-side filters
2-
:page-aliases: docs@starlight-for-jms::pulsar-jms-server-side-filters.adoc
2+
:page-aliases: docs@starlight-jms::pulsar-jms-server-side-filters.adoc
33

44
{starlight_jms} version {product_version} offers *server-side filtering*, which executes JMS filtering features on the Pulsar Broker instead of the Client. +
55
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.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
= Installing {starlight_jms}
22

33
:page-tag: starlight-jms,install,dev,admin,pulsar,jms,java,maven
4-
:page-aliases: docs@starlight-for-jms::pulsar-jms-install.adoc
4+
:page-aliases: docs@starlight-jms::pulsar-jms-install.adoc
55
== Compatibility
66

77
The current version of {starlight_jms} is {product_version}. Version {product_version} includes:

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
= {starlight_jms} Astra Streaming quick start
22

33
:page-tag: starlight-jms,dev,quickstart,pulsar,jms
4-
:page-aliases: docs@starlight-for-jms::pulsar-jms-quickstart-astra.adoc
4+
:page-aliases: docs@starlight-jms::pulsar-jms-quickstart-astra.adoc
55

66
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:
77

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
= {starlight_jms} standalone quick start
22

33
:page-tag: starlight-jms,dev,quickstart,pulsar,java,jms
4-
:page-aliases: docs@starlight-for-jms::pulsar-jms-quickstart-sa.adoc
4+
:page-aliases: docs@starlight-jms::pulsar-jms-quickstart-sa.adoc
55

66
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:
77

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
= Mapping Pulsar concepts to JMS specifications
22

33
:page-tag: starlight-jms,planner,dev,admin,pulsar,jms
4-
:page-aliases: docs@starlight-for-jms::pulsar-jms-mappings.adoc
4+
:page-aliases: docs@starlight-jms::pulsar-jms-mappings.adoc
55

66
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.
77

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
= {starlight_jms} configuration reference
22

33
:page-tag: starlight-jms,dev,admin,manage,pulsar,jms
4-
:page-aliases: docs@starlight-for-jms::pulsar-jms-reference.adoc
4+
:page-aliases: docs@starlight-jms::pulsar-jms-reference.adoc
55

66
A complete configuration reference for {starlight_jms}.
77

0 commit comments

Comments
 (0)