From 403690eb21eab6b7cecc64fbe0cc6cb2184a3294 Mon Sep 17 00:00:00 2001 From: Tran Ngoc Nhan Date: Mon, 7 Jul 2025 02:21:55 +0700 Subject: [PATCH] Fix typos Signed-off-by: Tran Ngoc Nhan --- .../ROOT/pages/kafka/receiving-messages/filtering.adoc | 2 +- .../antora/modules/ROOT/pages/kafka/sending-messages.adoc | 2 +- .../main/antora/modules/ROOT/pages/retrytopic/features.adoc | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/spring-kafka-docs/src/main/antora/modules/ROOT/pages/kafka/receiving-messages/filtering.adoc b/spring-kafka-docs/src/main/antora/modules/ROOT/pages/kafka/receiving-messages/filtering.adoc index 17ed26da9b..8dad74423a 100644 --- a/spring-kafka-docs/src/main/antora/modules/ROOT/pages/kafka/receiving-messages/filtering.adoc +++ b/spring-kafka-docs/src/main/antora/modules/ROOT/pages/kafka/receiving-messages/filtering.adoc @@ -29,7 +29,7 @@ public void listen(Thing thing) { Starting with version 3.3, Ignoring empty batches that result from filtering by `RecordFilterStrategy` is supported. When implementing `RecordFilterStrategy`, it can be configured through `ignoreEmptyBatch()`. -The default setting is `false`, indicating `KafkaListener` will be invoked even if all `ConsumerRecord` s are filtered out. +The default setting is `false`, indicating `KafkaListener` will be invoked even if all ``ConsumerRecord``s are filtered out. If `true` is returned, the `KafkaListener` [underline]#will not be invoked# when all `ConsumerRecord` are filtered out. However, commit to broker, will still be executed. diff --git a/spring-kafka-docs/src/main/antora/modules/ROOT/pages/kafka/sending-messages.adoc b/spring-kafka-docs/src/main/antora/modules/ROOT/pages/kafka/sending-messages.adoc index 672015373b..3b46a0cdb9 100644 --- a/spring-kafka-docs/src/main/antora/modules/ROOT/pages/kafka/sending-messages.adoc +++ b/spring-kafka-docs/src/main/antora/modules/ROOT/pages/kafka/sending-messages.adoc @@ -558,7 +558,7 @@ Previously, the listener had to echo custom correlation headers. [[exchanging-messages]] === Request/Reply with `Message`+++s+++ -Version 2.7 added methods to the `ReplyingKafkaTemplate` to send and receive `spring-messaging` 's `Message` abstraction: +Version 2.7 added methods to the `ReplyingKafkaTemplate` to send and receive ``spring-messaging``'s `Message` abstraction: [source, java] ---- diff --git a/spring-kafka-docs/src/main/antora/modules/ROOT/pages/retrytopic/features.adoc b/spring-kafka-docs/src/main/antora/modules/ROOT/pages/retrytopic/features.adoc index 429d65e8db..fcf4ccdbe5 100644 --- a/spring-kafka-docs/src/main/antora/modules/ROOT/pages/retrytopic/features.adoc +++ b/spring-kafka-docs/src/main/antora/modules/ROOT/pages/retrytopic/features.adoc @@ -87,7 +87,7 @@ public RetryTopicConfiguration myRetryTopic(KafkaTemplate templa } ---- -NOTE: The default is having no timeout set, which can also be achieved by providing -1 as the timout value. +NOTE: The default is having no timeout set, which can also be achieved by providing -1 as the timeout value. [[retry-topic-ex-classifier]] == Exception Classifier @@ -250,9 +250,9 @@ Starting with version 3.0.9, you can override the `RetryTopicConfigurationSuppor [source, java] ---- @Override -protected Consumer +protected Consumer configureDeadLetterPublishingContainerFactory() { - + return (factory) -> factory.setDeadLetterPublisherCreator( (templateResolver, destinationResolver) -> new CustomDLPR(templateResolver, destinationResolver));