Skip to content

Spring Integration 5.1 to 5.2 Migration Guide

Jump to bottom
Gary Russell edited this page Jul 29, 2019 · 10 revisions

Table of Contents

Deprecated ChannelInterceptorAware

The ChannelInterceptorAware has been deprecated in favor of org.springframework.messaging.support.InterceptableChannel with exact functionality. A protected AbstractMessageChannel.getInterceptors() method to obtain an internal AbstractMessageChannel.ChannelInterceptorList has been renamed to the getIChannelInterceptorList() since it clashes with the InterceptableChannel.getInterceptors() and they have a different return types. The VetoCapableInterceptor.shouldIntercept() signature has been changed to accept an InterceptableChannel already.

JDBC Outbound Gateway maxRows

If the maxRows for the JdbcOutboundGateway is > 1, the query result is returned as a List even if it contains only one item. Previously when only one item was retrieved the payload was the item itself, independent of the maxRows configuration. Always returning a list makes user code simpler, but this change may break some existing applications. Most likely, however, it won't because, presumably, such apps would always check for both an object or a list of objects; this is no longer necessary since it will always be a list.

DSL publishSubscribeChannel Behavior Change

Given the following IntegrationFlow:

return f -> f
        .publishSubscribeChannel(c -> c
                .subscribe(sf -> sf.handle(...)
                .subscribe(sf -> sf.handle(...)
                .subscribe(sf -> sf.handle(...))
                ...

If this flow is defined in a static @Bean definition, the subscribers are invoked in the natural (first to last) order.

However, with previous releases, if the flow is registered dynamically with the IntegrationFlowContext, the subscribers were invoked last to first.

Starting with the 5.2 release, the subscribers are invoked in the natural (first to last) order, regardless of static Vs. dynamic registration.

Clone this wiki locally