Spring Blog

A support for Spring Native compatibility - a lot of bean definition reflection has been reworked to the functional style, which improves a start up time even for regular JVM application!

The FileAggregator component was introduced. See its JavaDocs for more info;

All the persistent MessageGroupStore implementations provide a streamMessagesForGroup(Object groupId) contract based on the target database streaming API;

The integrationGlobalProperties custom bean now has to be an instance of org.springframework.integration.context.IntegrationProperties instead of deprecated java.util.Properties representation. All these Integration properties are now exposed as auto-configuration properties in Spring Boot;

The maxMessagesPerPoll == 0 for an AbstractPollingEndpoint is treated now as to skip calling the source;

A @Reactive sub-annotation was introduced for annotation configuration to apply a Function<? super Flux<Message<?>>, ? extends Publisher<Message<?>>> reactiveCustomizer for underlying consumer endpoint and make it as reactive independently of the input channel. Same behavior can be achieved in Java DSL via ConsumerEndpointSpec.reactive() option;

MongoDb message sources now have an optional update to mark document which have just been pulled from the collection;

WebSocket server endpoint-based channel adapters can now be registered (and removed) at runtime;

The MessageGroup abstraction has now a condition property which can be consulted later on instead of the whole group iteration. The AbstractCorrelatingMessageHandler, in turn, exposes a BiFunction<Message<?>, String, String> conditionSupplier to extract possible group condition from the currently processed message;

The DelayHandler now registers a TransactionSynchronization to schedule a delay task only when current transaction is committed;

The GreenMail library is used now for email integration tests.