From 79cafcae1ba673b799d4f37b069f2353936802d4 Mon Sep 17 00:00:00 2001 From: Antonio Goncalves Date: Wed, 23 Sep 2020 14:09:58 +0200 Subject: [PATCH] KafkaMessage is deprecated use KafkaRecord instead `io.smallrye.reactive.messaging.kafka.KafkaMessage` is marked as deprecated linking to `io.smallrye.reactive.messaging.kafka.KafkaRecord` --- spec/src/main/asciidoc/architecture.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/src/main/asciidoc/architecture.asciidoc b/spec/src/main/asciidoc/architecture.asciidoc index e15e8f71..000e7725 100644 --- a/spec/src/main/asciidoc/architecture.asciidoc +++ b/spec/src/main/asciidoc/architecture.asciidoc @@ -65,7 +65,7 @@ Reactive Messaging application components are addressable recipients which await Messages are represented by the `org.eclipse.microprofile.reactive.messaging.Message` class. This interface is intentionally kept minimal. The aim is that _connectors_ will provide their own implementations with additional metadata that is relevant to that connector. -For instance, a `KafkaMessage` would provide access to the _topic_ and _partition_. +For instance, a `KafkaRecord` would provide access to the _topic_ and _partition_. The `org.eclipse.microprofile.reactive.messaging.Message#getPayload` method retrieves the wrapped payload. The `org.eclipse.microprofile.reactive.messaging.Message#ack` method acknowledges the message.