pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From si...@apache.org
Subject [pulsar] branch master updated: Fix broken reference (#3796)
Date Mon, 11 Mar 2019 01:20:08 GMT
This is an automated email from the ASF dual-hosted git repository.

sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git


The following commit(s) were added to refs/heads/master by this push:
     new b46e3e3  Fix broken reference (#3796)
b46e3e3 is described below

commit b46e3e3789eaa008b79af56521fe55f93763f46f
Author: Like <like_0903@163.com>
AuthorDate: Mon Mar 11 09:20:03 2019 +0800

    Fix broken reference (#3796)
    
    Fix broken @inject link and ```reader-interface``` reference in http://pulsar.apache.org/docs/en/client-libraries-java/
---
 site2/docs/client-libraries-java.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/site2/docs/client-libraries-java.md b/site2/docs/client-libraries-java.md
index b8680d8..4c4261f 100644
--- a/site2/docs/client-libraries-java.md
+++ b/site2/docs/client-libraries-java.md
@@ -4,7 +4,7 @@ title: The Pulsar Java client
 sidebar_label: Java
 ---
 
-The Pulsar Java client can be used both to create Java producers, consumers, and [readers](#readers)
of messages and to perform [administrative tasks](admin-api-overview.md). The current version
of the Java client is **{{pulsar:version}}**.
+The Pulsar Java client can be used both to create Java producers, consumers, and [readers](#reader-interface)
of messages and to perform [administrative tasks](admin-api-overview.md). The current version
of the Java client is **{{pulsar:version}}**.
 
 Javadoc for the Pulsar client is divided up into two domains, by package:
 
@@ -128,7 +128,7 @@ stringProducer.send("My message");
 
 ### Configuring producers
 
-If you instantiate a `Producer` object specifying only a topic name, as in the example above,
the producer will use the default configuration. To use a non-default configuration, there's
a variety of configurable parameters that you can set. For a full listing, see the Javadoc
for the {@inject javadoc:ProducerBuilder:/client/org/apache/pulsar/client/api/ProducerBuilder}
class. Here's an example:
+If you instantiate a `Producer` object specifying only a topic name, as in the example above,
the producer will use the default configuration. To use a non-default configuration, there's
a variety of configurable parameters that you can set. For a full listing, see the Javadoc
for the {@inject: javadoc:ProducerBuilder:/client/org/apache/pulsar/client/api/ProducerBuilder}
class. Here's an example:
 
 ```java
 Producer<byte[]> producer = client.newProducer()
@@ -155,7 +155,7 @@ producer.sendAsync("my-async-message".getBytes()).thenAccept(msgId ->
{
 });
 ```
 
-As you can see from the example above, async send operations return a {@inject javadoc:MessageId:/client/org/apache/pulsar/client/api/MessageId}
wrapped in a [`CompletableFuture`](http://www.baeldung.com/java-completablefuture).
+As you can see from the example above, async send operations return a {@inject: javadoc:MessageId:/client/org/apache/pulsar/client/api/MessageId}
wrapped in a [`CompletableFuture`](http://www.baeldung.com/java-completablefuture).
 
 ### Configuring messages
 
@@ -232,7 +232,7 @@ Here's an example:
 CompletableFuture<Message> asyncMessage = consumer.receiveAsync();
 ```
 
-Async receive operations return a {@inject javadoc:Message:/client/org/apache/pulsar/client/api/Message}
wrapped inside of a [`CompletableFuture`](http://www.baeldung.com/java-completablefuture).
+Async receive operations return a {@inject: javadoc:Message:/client/org/apache/pulsar/client/api/Message}
wrapped inside of a [`CompletableFuture`](http://www.baeldung.com/java-completablefuture).
 
 ### Multi-topic subscriptions
 
@@ -306,9 +306,9 @@ consumerBuilder
         });
 ```
 
-## Reader interface {#readers}
+## Reader interface
 
-With the [reader interface](concepts-clients.md#reader-interface), Pulsar clients can "manually
position" themselves within a topic, reading all messages from a specified message onward.
The Pulsar API for Java enables you to create  {@inject: javadoc:Reader:/client/org/apache/pulsar/client/api/Reader}
objects by specifying a topic, a {@inject: javadoc:MessageId:/client/org/apache/pulsar/client/api/MessageId},
and {@inject javadoc:ReaderConfiguration:/client/org/apache/pulsar/client/api/ [...]
+With the [reader interface](concepts-clients.md#reader-interface), Pulsar clients can "manually
position" themselves within a topic, reading all messages from a specified message onward.
The Pulsar API for Java enables you to create  {@inject: javadoc:Reader:/client/org/apache/pulsar/client/api/Reader}
objects by specifying a topic, a {@inject: javadoc:MessageId:/client/org/apache/pulsar/client/api/MessageId},
and {@inject: javadoc:ReaderConfiguration:/client/org/apache/pulsar/client/api [...]
 
 Here's an example:
 


Mime
View raw message