Spring Integration 4.2 to 4.3 Migration Guide

Outbound Gateway within Chain

Previously, it was possible to specify a reply-channel on an <outbound-gateway> within a <chain>. It was completely ignored; the gateway's reply goes to the next chain element, or to the chain's output-channel if the gateway is the last element. This condition is now detected and disallowed. If you have such configuration, simply remove the reply-channel.

Redis Queue Inbound Gateway

The default serializer in the RedisQueueInboundGateway has been changed to a JdkSerializationRedisSerializer for compatibility with the RedisQueueOutboundGateway for client/server interaction scenarios. Previously it was (in the RedisQueueInboundGateway) a StringRedisSerializer by default; to restore that behavior provide a reference to a its bean.

Global Properties

In previous versions, the Integration property names had a typographical error (...integraton...); they have now been corrected (...integration...). So, now this properties looks like with their default values:

spring.integration.channels.autoCreate=true
spring.integration.channels.maxUnicastSubscribers=0x7fffffff
spring.integration.channels.maxBroadcastSubscribers=0x7fffffff
spring.integration.taskScheduler.poolSize=10
spring.integration.messagingTemplate.throwExceptionOnLateReply=false
spring.integration.messagingAnnotations.require.componentAnnotation=false

See Reference Manual for more information.

Messaging Annotation Support and @Component

Previously, the @MessageEndpoint stereotype annotation (or any other @Component) has been required on the class level to process Messaging Annotations like @ServiceActivator, @TRansformer, @InboundChannelAdapter, @Splitter etc. from the class methods. Right now this restriction has been removed. To restore the requirement, and therefore the previous Spring Integration behavior, consider to specify Spring Integration property spring.integration.messagingAnnotations.require.componentAnnotation as true in the spring.integration.properties file.