What’s New?

For those who are already familiar with Spring Integration, this chapter provides a brief overview of the new features of version 5.3.

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.3?

If you are interested in more details, see the Issue Tracker tickets that were resolved as part of the 5.3 development process.

New Components

Integration Pattern

The IntegrationPattern abstraction has been introduced to indicate which enterprise integration pattern (an IntegrationPatternType) and category a Spring Integration component belongs to. See its JavaDocs and Integration Graph for more information about this abstraction and its use-cases.

`ReactiveMessageHandler`

The ReactiveMessageHandler is now natively supported in the framework. See ReactiveMessageHandler for more information.

Java DSL Extensions

A new IntegrationFlowExtension API has been introduced to allow extension of the existing Java DSL with custom or composed EIP-operators. This also can be used to introduce customizers for any out-of-the-box IntegrationComponentSpec extensions. See DSL Extensions for more information.

MongoDB Reactive Channel Adapters

spring-integration-mongodb module now provides channel adapter implementations for Reactive MongoDB driver support in Spring Data. See MongoDB Reactive Channel Adapters for more information.

General Changes

The gateway proxy now doesn’t proxy default methods by default. See Invoking default Methods for more information.

Internal components (such as _org.springframework.integration.errorLogger) now have a shortened name when they are represented in the integration graph. See Integration Graph for more information.

In the aggregator, when the MessageGroupProcessor returns a Message, the MessageBuilder.popSequenceDetails() is performed on the output message if the sequenceDetails matches the header in the first message of the group. See Aggregator Programming Model for more information.

AMQP Changes

The outbound channel adapter has a new property multiSend allowing multiple messages to be sent within the scope of one RabbitTemplate invocation. See AMQP Outbound Channel Adapter for more information.

The inbound channel adapter now supports a listener container with the consumerBatchEnabled property set to true. See AMQP Inbound Channel Adapter

HTTP Changes

The encodeUri property on the AbstractHttpRequestExecutingMessageHandler has been deprecated in favor of newly introduced encodingMode. See DefaultUriBuilderFactory.EncodingMode JavaDocs and Controlling URI Encoding for more information. This also effects WebFluxRequestExecutingMessageHandler, respective Java DSL and XML configuration.