-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Spring Integration 2.0 to 2.1 Migration Guide
For reference see: https://jira.springsource.org/browse/INT-2324
Spring Integration 2.1 now depends (As a minimum) on Spring 3.0.7.RELEASE. Spring Integration 2.1 will also work with Spring 3.1.0.RELEASE.
The following dependencies were updated between Spring Integration 2.0.5.RELEASE and 2.1:
Dependency | Old Version | New Version |
---|---|---|
Commons Net | 2.0 | 3.0.1 |
Jackson | 1.4.3 | 1.8.3 |
Spring | 3.0.5.RELEASE | 3.0.7.RELEASE |
Spring Security | 3.0.5.RELEASE | 3.1.0.RELEASE |
Spring Web Services | 2.0.2.RELEASE | 2.0.3.RELEASE |
Groovy | 1.7.5 | 1.8.4 |
JSch | 0.1.42 | 0.1.45 |
The Spring Integration Twitter Module now uses Spring Social 1.0.1.RELEASE, instead of Twitter4j.
Spring Integration 2.1 ships with an updated version 2.1 XML Schema. Users must make sure to use either version-less XML Spring Integration namespaces or to use the 2.1 XML namespace. If you try to use a Spring Integration 2.1 based application with the old 2.0 or 1.0 XML namespace, an exception will be thrown:
The 'spring-integration-httpinvoker' module, which was deprecated in version 2.0, has been removed with Spring Integration 2.1.
Since Spring Integration 2.1 the ignore-channel-name-resolution-failures attribute is removed in favor of consolidating its behavior with the resolution-required attribute. Also, the resolution-required attribute now defaults to true. Prior to these changes, the resolution-required attribute defaulted to false causing messages to be silently dropped when no channel was resolved and no default-output-channel was set. The new behavior will require at least one resolved channel and by default will throw a MessageDeliveryException if no channel was determined (or an attempt to send was not successful).
If you desire to drop messages silently simply set:
default-output-channel="nullChannel"