fix: resolve BeanPostProcessors auto-proxy warning (#257)#258
Open
Fhui wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
修复 Spring Boot 3.x 启动时的 BeanPostProcessors auto-proxy 警告(#257)
在 Spring Boot 3.4 / Spring 6.2 环境下,应用启动时会出现以下警告:
not eligible for getting processed by all BeanPostProcessors (for example: not eligible to auto-proxying).
Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [forestBeanProcessor]?
总结您的更改
调整 Bean 注册流程, 修复启动阶段的 BeanPostProcessors 警告, 同步修复 Boot2 Starter 中相同的问题, 保持行为一致.
最后新增回归测试, 验证启动时不再出现该警告.
请注明您已完成以下工作: