-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Spring Integration 5.0 to 5.1 Migration Guide
- move
StaticMessageHeaderAccessorto rootintegrationpackage - move acknowledgment related classes to a new
ackspackage - move
MMIHtohandler.support, alongside argument resolvers, alsoHandlerMethodArgumentResolversHolder - move
ErrorMessagePublishertocore - move
PatternMatchUtilstosupport.utils - move
MessageSourceManagementtosupport.management - remove direct reference to
MicrometerMetricsCapterfromIntegrationManagementSupport - add new class
MetricsCaptorLoader - move
OperationsCallbackto inner interface inRemoteFileOperations - move
HttpContextUtilstoconfig - move
IntegrationManagementConfigurerfrommanagementtoconfig - make
grapha top-level package - move classes from
config.dslpackage todslone - rename core
eventpackage toevents
The IntegrationFlowContext is now an interface and IntegrationFlowRegistration is an inner interface of the IntegrationFlowContext.
Exceptions caught and re-thrown by AbstractDispatcher are now more consistent:
- A
MessagingExceptionof any kind, with afailedMessageproperty, is re-thrown unchanged - All other exceptions are wrapped in a
MessageDeliveryExceptionwith thefailedMessageproperty set
Previously:
- A
MessagingExceptionof any kind, with afailedMessageproperty, was re-thrown unchanged - A
MessagingException, with nofailedMessageproperty, was wrapped in aMessagingExceptionwith thefailedMessageproperty set - Other
RuntimeExceptions were re-thrown unchanged - Checked exceptions were wrapped in a
MessageDeliveryExceptionwith thefailedMessageproperty set
An integrationSimpleEvaluationContext bean for the SimpleEvaluationContext is register now alongside with the integrationEvaluationContext bean for the StandardEvaluationContext. Therefore an injection for the EvaluationContext should be reconsidered for the appropriate bean to use.
Right now this module is based on the Open Source Spring Data for Apache Geode project as transitive dependency.
To switch to the commercial Pivotal GemFire based Spring Data for Pivotal GemFire, exclude spring-data-geode from dependencies and add spring-data-gemfire:
<dependency>
<groupId>org.springframework.integration</groupId>
<artifactId>spring-integration-gemfire</artifactId>
<exclusions>
<exclusion>
<groupId>org.springframework.data</groupId>
<artifactId>spring-data-geode</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.springframework.data</groupId>
<artifactId>spring-data-gemfire</artifactId>
</dependency>