the issue of doCreateBean

[799332391]

org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory#doCreateBean

if (earlySingletonExposure) {
			Object earlySingletonReference = getSingleton(beanName, false);
			if (earlySingletonReference != null) {
				if (exposedObject == bean) {
					exposedObject = earlySingletonReference;
				}

exposedObject = earlySingletonReference;
If this assignment is indeed not redundant, it suggests that the custom getEarlyBeanReference method results in the reference no longer pointing to the final, fully initialized bean. Consequently, would the subsequent execution of registered bean destruction callbacks become unnecessary in this scenario?

[bclozel]

This report is quite similar to #29756

Rather than reading the code and thinking about potential issues, we would rather look at a concrete example where you can demonstrate a problem.

[799332391]

I didn't say that this line of code has execution problems. It's just that after considering the context, I felt a bit confused about this line. I have read #29756, and my reply and question are also based on #29756. The replies in #29756 at least explained some of the reasons, but your reply doesn't provide any substantial explanation.

[bclozel]

Thanks but we'd rather spend time on actual issues and enhancements reported by the community. Explaining the codebase line by line is not our top priority. If you think there is a behavior problem with this code, you can probably illustrate it with a simple application and share it with us.

[799332391]

demo2.zip

[799332391]

Please set a breakpoint at this line of code in AbstractAutowireCapableBeanFactory.java: exposedObject = earlySingletonReference;. Add a breakpoint condition: beanName.contains("serviceA"). Then, compare the execution results with the MyProcessor class commented out and not commented out.