Spring/spring-pulsar
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify use of MessageResult vs. MessageUtils (#681)

Browse Source 
Updates the reactive-message-consumption.adoc to clarify the difference
between the factory methods on `MessageResult` and `MessageUtils`.

Resolves #666
This commit is contained in:
Chris Bono
2024-05-20 11:12:43 -05:00
committed by GitHub
parent c87dbf7af7
commit 0454c8df7e
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
spring-pulsar-docs/src/main/antora/modules/ROOT/pages/reference/reactive-pulsar/reactive-message-consumption.adoc
View File

@@ -111,6 +111,7 @@ Flux<MessageResult<Void>> listen2(Flux<org.springframework.messaging.Message<Foo
NOTE: The listener method returns a `Flux<MessageResult<Void>>` where each element represents a processed message and holds the message id, value and whether it was acknowledged.
The Spring `MessageUtils` has a set of static factory methods that can be used to create the appropriate `MessageResult` instance from a Spring message.
The `MessageUtils` provides the same functionality for Spring messages as the set of factory methods on `MessagResult` does for Pulsar messages.
NOTE: There is no support for using `org.apache.pulsar.client.api.Messages<T>` in a `@ReactivePulsarListener`