diff --git a/spring-pulsar-docs/src/main/antora/modules/ROOT/pages/reference/reactive-pulsar/reactive-message-consumption.adoc b/spring-pulsar-docs/src/main/antora/modules/ROOT/pages/reference/reactive-pulsar/reactive-message-consumption.adoc index 99e0cc3e..48ed9144 100644 --- a/spring-pulsar-docs/src/main/antora/modules/ROOT/pages/reference/reactive-pulsar/reactive-message-consumption.adoc +++ b/spring-pulsar-docs/src/main/antora/modules/ROOT/pages/reference/reactive-pulsar/reactive-message-consumption.adoc @@ -112,6 +112,8 @@ Flux> listen2(Flux>` 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. +NOTE: There is no support for using `org.apache.pulsar.client.api.Messages` in a `@ReactivePulsarListener` + === Configuration - Application Properties The listener relies on the `ReactivePulsarConsumerFactory` to create and manage the underlying Pulsar consumer that it uses to consume messages. Spring Boot provides this consumer factory which you can further configure by specifying the {spring-boot-pulsar-config-props}[`spring.pulsar.consumer.*`] application properties. diff --git a/spring-pulsar-docs/src/main/antora/modules/ROOT/pages/reference/tombstones-reactive.adoc b/spring-pulsar-docs/src/main/antora/modules/ROOT/pages/reference/tombstones-reactive.adoc index 93ba86a7..3eba8602 100644 --- a/spring-pulsar-docs/src/main/antora/modules/ROOT/pages/reference/tombstones-reactive.adoc +++ b/spring-pulsar-docs/src/main/antora/modules/ROOT/pages/reference/tombstones-reactive.adoc @@ -36,7 +36,7 @@ For `@ReactivePularListener`, the `null` payload is passed into the listener met | `Flux>` | non-null flux whose entries are non-null Pulsar messages whose `getValue()` returns `null` -| `Flux>` +| `Flux>` | non-null flux whose entries are non-null Spring messages whose `getPayload()` returns `PulsarNull` |===