spring-projects / spring-projects/spring-framework
the issue of doCreateBean
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 60.2k
- Forks
- 38.8k
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 27
Description
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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory#doCreateBean and inspect the earlySingletonExposure branch, especially the assignment to exposedObject. Determine whether getEarlyBeanReference can make the exposed reference differ from the fully initialized bean and whether destruction callbacks are still required. Done means resolving whether the behavior is redundant or incorrect and documenting or correcting the confirmed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100