[#1892] Adjust Upcaster ordering logic in Spring environments #1895
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.
The current solution in the
SpringAxonAutoConfigurer
will not check whether a bean creation method has the@Order
annotation.It instead only works if the
@Order
annotation is added to the class of the upcaster itself.Although this works fine, allowing the
@Order
annotation to be paired with the@Bean
annotation is friendlier.This pull request adjusts the behavior in the
SpringAxonAutoConfigurer
such that we look for the@Order
annotation through theListableBeanFactory#findAnnotationOnBean(String beanName, Class<A> annotationClass)
.This method takes bean creation methods into account, hence allowing us to check for the order on those.
With these adjustments, issue #1892 is resolved.