Deprecation doc polishing

Channel interceptors.
This commit is contained in:
Gary Russell
2018-04-10 18:58:52 -04:00
committed by Artem Bilan
parent d807fc3692
commit 6216075619
3 changed files with 11 additions and 0 deletions

View File

@@ -294,6 +294,9 @@ Starting with _Spring Framework 4.1_ and Spring Integration 4.1, the `ChannelInt
They are invoked after `send()/receive()` calls, regardless of any exception that is raised, thus allowing for resource cleanup.
Note, the Channel invokes these methods on the ChannelInterceptor List in the reverse order of the initial `preSend()/preReceive()` calls.
Starting with _version 5.1_, global channel interceptors are now applied to channels registered dynamically - such as via the `IntegrationFlowContext` when using the Java DSL, or beans that are initialized using `beanFactory.initializeBean()`.
Previously, interceptors were not applied when beans were created after the application context was refreshed.
[[channel-template]]
==== MessagingTemplate

View File

@@ -413,6 +413,9 @@ This annotation is an analogue of the `<int:channel-interceptor>` xml element (s
`@GlobalChannelInterceptor` annotations can be placed at the class level (with a `@Component` stereotype annotation), or on `@Bean` methods within `@Configuration` classes.
In either case, the bean *must* be a `ChannelInterceptor`.
Starting with _version 5.1_, global channel interceptors are now applied to channels registered dynamically - such as via the `IntegrationFlowContext` when using the Java DSL, or beans that are initialized using `beanFactory.initializeBean()`.
Previously, interceptors were not applied when beans were created after the application context was refreshed.
The `@IntegrationConverter` annotation has been introduced to mark `Converter`, `GenericConverter` or `ConverterFactory` beans as candidate converters for `integrationConversionService`.
This annotation is an analogue of the `<int:converter>` xml element (see <<payload-type-conversion>>).
`@IntegrationConverter` annotations can be placed at the class level (with a `@Component` stereotype annotation), or on `@Bean` methods within `@Configuration` classes.

View File

@@ -33,3 +33,8 @@ Previously:
- A `MessagingException`, with no `failedMessage` property, was wrapped in a `MessagingException` with the `failedMessage` property set
- Other `RuntimeException` s were re-thrown unchanged
- Checked exceptions were wrapped in a `MessageDeliveryException` with the `failedMessage` property set
==== Global Channel Interceptors
Global channel interceptors are now applied to channels registered dynamically - such as via the `IntegrationFlowContext` when using the Java DSL, or beans that are initialized using `beanFactory.initializeBean()`.
Previously, interceptors were not applied when beans were created after the application context was refreshed.