INT-3672: Fix IdempotentReceiver for MH @Beans
#1405
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JIRA: https://jira.spring.io/browse/INT-3672 Previously the `IdempotentReceiverInterceptor` has been applied only for the `MessageHandler`s which were registered with `.handler` suffix. Rework `IdempotentReceiverAutoProxyCreatorInitializer` and `IdempotentReceiverAutoProxyCreator` to get deal with **direct** `MessageHandler`s which can be resulted from `@Bean` methods. Use the `MessageHandler` real bean name instead of `endpoint pattern` in that case **Cherry-pick to 4.1.x**
|
Merged and cherry-picked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JIRA: https://jira.spring.io/browse/INT-3672
Previously the
IdempotentReceiverInterceptorhas been applied only for theMessageHandlers which were registered with.handlersuffix.Rework
IdempotentReceiverAutoProxyCreatorInitializerandIdempotentReceiverAutoProxyCreatorto get deal with directMessageHandlerswhich can be resulted from
@Beanmethods.Use the
MessageHandlerreal bean name instead ofendpoint patternin that caseCherry-pick to 4.1.x