create migration guide for those upgrading to 2.1 [INT-2324]

[spring-operator]

Mark Fisher opened INT-2324 and commented

---

No further details from INT-2324

[spring-operator]

Mark Fisher commented

should mention the need to migrate data if a MessageGroupQueue had been used since the new groupId will have [messageStoreId].[channelName] (whereas the previous version had [packageName].[channelName])

[spring-operator]

Mark Fisher commented

handlers within a chain are no longer registered as beans, and therefore would not be exposed directly as MBeans (the chain is effectively a black box)

[spring-operator]

Mark Fisher commented

Gunnar, I'll assign this one to you, but it will require some collaboration amongst all of us. Let's start by adding the comments here as to what we need to be sure is covered.

[spring-operator]

Mark Fisher commented

Anyone extending AbstractMessageRouter might need to modify code now that there is a new level for AbstractMappingMessageRouter which also renamed getChannelIdentifiers() to getChannelMappings(). That method is now only needed for mapping router extensions though.

[spring-operator]

Gary Russell commented

And Routers that are not mapping routers (extend AMR), need to implement determineTargetChannels (returning null if the desire is to route to the discard channel).

[spring-operator]

Gunnar Hillert commented

User must make sure to use either version-less XML Spring Integration namespaces or to use the 2.1 XML namespace.

[spring-operator]

Gunnar Hillert commented

Router Changes

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 an MessageDeliveryException if no channel was determined (or an attempt to send was not successful).
If you do desire to drop messages silently simply set default-output- channel="nullChannel".

[spring-operator]

Gunnar Hillert commented

See also: https://github.com/SpringSource/spring-integration/wiki/Spring-Integration-2.0-to-2.1-Migration-Guide

[spring-operator]

Mark Fisher commented

A couple comments:

1. Even though we have Spring 3.0.7 as our explicit dependency, I don't think we are depending directly on anything new since 3.0.5.

2. Under "Poller Changes" you mention: "The following previously deprecated XML attributes were removed in Spring Integration 2.1:..." However it was sub-elements that were deprecated, and we should also mention the new alternative which is 'cron', 'fixed-delay' or 'fixed-rate' attribute (or a 'trigger' reference attribute).

[spring-operator]

Gunnar Hillert commented

Made the changes to: https://github.com/SpringSource/spring-integration/wiki/Spring-Integration-2.0-to-2.1-Migration-Guide