4.0 Migration guide

No more Annotations

In version 2.0 we have introduced functional programming style for implementing message handlers. For several versions we have supported both functional and annotation-based model. Since version 4.0 annotation-based programming model is removed Here is how you should migrate your old StreamListener to. . . . TBD. .

Binding specific error channel naming scheme

• Old scheme created a possibility of naming collision since it was not unique. The <destination>.<group>.errors relies on the fact that destination name is uniques across the application. However that is not the case since it could have the same name across tow different messaging systems. Further more destination naming is not something that is under control of the user, rather messaging system administrator TBD. . .

Reactive functions vs Imperative

Not really a migration issue, but we need to explain the fundamental difference between these two types of programming models and the impact it has on the framework-based expectations user has