GH-3467: Fix KafkaListenerAnnotationBeanPostProcessor for early BF access #3468
+6
−8
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: #3467
The
KafkaListenerAnnotationBeanPostProcessor.afterPropertiesSet()
get access toBeanFactory
for other beans which causes a warning into logs like:The rule of thumb is to not have any bean factory access from
BeanPostProcessor
initialization phaseKafkaListenerAnnotationBeanPostProcessor
tobuildEnhancer()
i lazy manner. Therefore remove anafterPropertiesSet()
altogetherAuto-cherry-pick to
3.2.x
&3.1.x