GH-10345: Migrate AMQP module into Spring Core Retry #10361
Merged
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.
Related to: #10345
The Spring Retry project is in its sunset.
There is an alternative in
spring-core
.org.springframework.integration.core.RecoveryCallback
as an alternative toRecoveryCallback
from Spring RetryAmqpInboundChannelAdapter
&AmqpInboundGateway
to always populateATTRIBUTES_HOLDER
when there is anerrorChannel
orretryTemplate
since Spring Core Retry does not operation with acontext
abstraction.ErrorMessageSendingRecoverer
based on the Spring IntegrationRecoveryCallback
.RequestHandlerRetryAdvice
to accept newRecoveryCallback
RecoveryCallback
APITODO
for subsequent fixes for this Replace the use of Spring Retry with Core Retry #10345