[lin-mt]

What is the purpose of the change

修复警告日志信息。 fix #723

在调用 applicationContext.getBean 的时候会提前初始化一些 Bean，这些 Bean 不会经过 BeanPostProcessor 处理，spring 会打印警告日志，使用构造器注入避免这个问题。

Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

• Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist.
• Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

[RockteMQ-AI]

Issue Evaluation

Category: bug | Status: Confirmed

This is a valid bug fix. The issue correctly identifies that calling applicationContext.getBean during certain lifecycle phases causes premature bean initialization, bypassing BeanPostProcessor and generating warning logs.

Root Cause: Direct getBean() calls trigger early initialization of beans that haven't gone through the full Spring lifecycle (including BeanPostProcessor processing).

Fix Approach: Switching to constructor injection is the correct solution — it lets Spring manage the dependency lifecycle properly and avoids the premature initialization warnings.

Impact: Eliminates spurious warning logs during startup; no functional behavior change.
Severity: Low — cosmetic/log noise issue, no data loss or correctness impact.

---

Automated evaluation by RockteMQ-AI