From 0cb1c57075476182627b0be7d85f1e73599263bf Mon Sep 17 00:00:00 2001 From: Marc DiPasquale Date: Fri, 14 Apr 2023 14:18:52 -0400 Subject: [PATCH] Add Solace updates --- docs/src/main/asciidoc/index.adoc | 1 + docs/src/main/asciidoc/spring-cloud-stream.adoc | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/index.adoc b/docs/src/main/asciidoc/index.adoc index 4ecb5e02c..16a80b75e 100644 --- a/docs/src/main/asciidoc/index.adoc +++ b/docs/src/main/asciidoc/index.adoc @@ -13,6 +13,7 @@ The reference documentation consists of the following sections: <> :: Spring Cloud Stream binder reference for Rabbit MQ <> :: Spring Cloud Stream binder reference for Apache Kafka <> :: Spring Cloud Stream binder reference for Apache Kafka Streams +https://github.com/SolaceProducts/solace-spring-cloud/tree/master/solace-spring-cloud-starters/solace-spring-cloud-stream-starter#spring-cloud-stream-binder-for-solace-pubsub[Solace PubSub+ Binder] :: Spring Cloud Stream binder reference for Solace PubSub+ (Partner Maintained) <> :: A collection of Partner maintained binder implementations for Spring Cloud Stream (e.g., Azure Event Hubs, Google PubSub, Solace PubSub+) <> :: Spring Cloud Stream Schema Registry Reference diff --git a/docs/src/main/asciidoc/spring-cloud-stream.adoc b/docs/src/main/asciidoc/spring-cloud-stream.adoc index 4ebf149b2..3ca6760f1 100644 --- a/docs/src/main/asciidoc/spring-cloud-stream.adoc +++ b/docs/src/main/asciidoc/spring-cloud-stream.adoc @@ -734,6 +734,8 @@ curl -H "Content-Type: text/plain" -X POST -d "hello from the other side" http:/ By showing two examples we want to emphasize the approach will work with any type of foreign sources. +NOTE: If you are using the Solace PubSub+ binder, Spring Cloud Stream has reserved the `scst_targetDestination` header (retrievable via BinderHeaders.TARGET_DESTINATION), which allows for messages to be redirected from their bindings' configured destination to the target destination specified by this header. This allows for the binder to manage the resources necessary to publish to dynamic destinations, relieving the framework from having to do so, and avoids the caching issues mentioned in the previous Note. More info https://github.com/SolaceProducts/solace-spring-cloud/tree/master/solace-spring-cloud-starters/solace-spring-cloud-stream-starter#dynamic-producer-destinations[here]. + ====== Output Content Type with StreamBridge You can also provide specific content type if necessary with the following method signature `public boolean send(String bindingName, Object data, MimeType outputContentType)`. @@ -2050,7 +2052,7 @@ You can also stop, start, pause, and resume individual bindings by posting to th curl -d '{"state":"RESUMED"}' -H "Content-Type: application/json" -X POST http://:/actuator/bindings/myBindingName NOTE: `PAUSED` and `RESUMED` work only when the corresponding binder and its underlying technology supports it. Otherwise, you see the warning message in the logs. -Currently, only Kafka binder supports the `PAUSED` and `RESUMED` states. +Currently, only Kafka and [Solace](https://github.com/SolaceProducts/solace-spring-cloud/tree/master/solace-spring-cloud-starters/solace-spring-cloud-stream-starter#consumer-bindings-pauseresume) binders supports the `PAUSED` and `RESUMED` states. === Binder Configuration Properties