For those who are already familiar with Spring Integration, this chapter provides a brief overview of the new features of version 5.2.
If you are interested in the changes and features that were introduced in earlier versions, see the Change History.
What’s New in Spring Integration 5.2?
If you are interested in more details, see the Issue Tracker tickets that were resolved as part of the 5.2 development process.
Rate Limit Advice Support
The RateLimiterRequestHandlerAdvice is now available for limiting requests rate on handlers.
See Rate Limiter Advice for more information.
Caching Advice Support
The CacheRequestHandlerAdvice is now available for caching request results on handlers.
See Caching Advice for more information.
Kotlin Scripts Support
The JSR223 scripting module now includes a support for Kotlin scripts. See Scripting Support for more information.
Flux Aggregator Support
The FluxAggregatorMessageHandler is now available for grouping and windowing messages logic based on the Project Reactor Flux operators.
See Flux Aggregator for more information.
General Changes
The JsonToObjectTransformer now supports generics for the target object to deserialize into.
See JSON Transformers for more information.
The splitter now supports a discardChannel configuration option.
See Splitter for more information.
The Control Bus can now handle Pausable (extension of Lifecycle) operations.
See Control Bus for more information.
AMQP Changes
The outbound endpoints can now be configured to synthesize a "nack" if no publisher confirm is received within a timeout. See Outbound Channel Adapter for more information.
The inbound channel adapter can now receive batched messages as a List<?> payload instead of receiving a discrete message for each batch fragment.
See Batched Messages for more information.
File Changes
Some improvements to filtering remote files have been made. See Remote Persistent File List Filters for more information.
TCP Changes
The length header used by the ByteArrayLengthHeaderSerializer can now include the length of the header in addition to the payload.
See Message Demarcation (Serializers and Deserializers) for more information.
When using a TcpNioServerConnectionFactory, priority is now given to accepting new connections over reading from existing connections, but it is configurable.
See About Non-blocking I/O (NIO) for more information.
The outbound gateway has a new property closeStreamAfterSend; when used with a new connection for each request/reply it signals EOF to the server, without closing the connection.
This is useful for servers that use the EOF to signal end of message instead of some delimiter in the data.
See TCP Gateways for more information.
The client connection factories now support connectTimeout which causes an exception to be thrown if the connection is not established in that time.
See TCP Connection Factories for more information.
Mail Changes
The AbstractMailReceiver has now an autoCloseFolder option (true by default), to disable an automatic folder close after a fetch, but populate IntegrationMessageHeaderAccessor.CLOSEABLE_RESOURCE header instead for downstream interaction.
See Mail-receiving Channel Adapter for more information.
WebFlux Changes
The WebFluxRequestExecutingMessageHandler now supports a Publisher, Resource and MultiValueMap as a request message payload.
See WebFlux Support for more information.
MongoDb Changes
The MongoDbMessageStore can now be configured with custom converters.
See MongoDB Support for more information.