GH-973: Higher order for RabbitListTestBootstrap #976
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.
Fixes #973
When we use
@EnableRabbit
and@RabbitListenerTest
in the sameconfiguration set, e.g. mixing real
@Configuration
and test one for@RabbitListenerTest
, we may end up with the case when@EnableRabbit
is processed before
@RabbitListenerTest
, so,RabbitListenerTestHarness
bean is not going to appear in the application context.
DeferredImportSelector
with an@Order
for the@EnableRabbit
as well asRabbitListenerTest
giving higher order tothe
RabbitListenerTestSelector
, soRabbitListenerTestBootstrap
isprocessed and register its
RabbitListenerTestHarness
earlier, than itis done by the
RabbitBootstrapConfiguration
Cherry-pick to 2.1.x