You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NOTE: This is a major release with several backward-incompatible changes
Specific Project Changes
Solace Spring Cloud Stream Binder
Breaking changes
Batch header name aligned with SCST standard (#453): The Solace-specific SolaceBinderHeaders.BATCHED_HEADERS has been replaced by the Spring Cloud Stream standard BinderHeaders.BATCH_HEADERS. Applications referencing SolaceBinderHeaders.BATCHED_HEADERS must be updated.
contentType header now stored as a Solace User Property (#452): The SCST contentType header is no longer mapped to the Solace standard header httpContentType. It is now stored and read as a Solace user property. Messages published with older versions of this binder may not have their contentType correctly round-tripped.
SolaceProducerProperties headerTypeCompatibility and payloadTypeCompatibility deprecated (#457): The default mode is now NATIVE_ONLY. In a future release, only NATIVE_ONLY mode will be supported. Applications that relied on automatic serialization mode must migrate.
solace_scst_messageVersion header conditionally removed (#461): Thesolace_scst_messageVersion header is no longer injected into published messages when both header and payload compatibility are set to NATIVE_ONLY (default now). The header is still added when non-native serialization is configured (i.e. SERIALIZE_AND_ENCODE_NON_NATIVE_TYPES for headers or SERIALIZE_NON_NATIVE_TYPES for payload) for backwards compatibility.
SOURCE_DATA header removed from ErrorMessage (#459): The raw Solace XMLMessage is no longer attached to error messages. Previously, the original Solace message was accessible via IntegrationMessageHeaderAccessor.SOURCE_DATA on the ErrorMessage. This header is no longer populated. Applications that accessed the original Solace message from error handlers via SOURCE_DATA must be updated.
Internal API visibility tightened (#462, #463): Internal classes and objects are now private or package-private. This reduces the public API surface and prevents accidental use of internal APIs. Applications relying on internal classes may be affected.
Documentation
Improved documentation on how to configure a pre-existing queue name (#460)
Fixed subscriptions from queueAdditionalSubscriptions not being added to the endpoint when addDestinationAsSubscription=false.
Fixed messages not being rejected/requeud when a function throws a MessagingException containing a failed message with its acknowledgmentCallback header removed.
Added the batchWaitStrategy consumer config option.
Fixed batchTimeout consumer config option in asynchronous consumers to be considered from when the first message is received, instead of when the last batch was processed.
