单例Bean对象

单例Bean对象

– >> finishBeanFactoryInitialization
实例化bean是放在finishBeanFactoryInitialization(beanFactory)方法中的。finishBeanFactoryInitialization方法中执行beanFactory.preInstantiateSingletons(),用于实例化所有非懒加载的单例bean.

protected void finishBeanFactoryInitialization(ConfigurableListableBeanFactory beanFactory) {
	// Initialize conversion service for this context.
	if (beanFactory.containsBean(CONVERSION_SERVICE_BEAN_NAME) &&
			beanFactory.isTypeMatch(CONVERSION_SERVICE_BEAN_NAME, ConversionService.class)) {
		beanFactory.setConversionService(
				beanFactory.getBean(CONVERSION_SERVICE_BEAN_NAME, ConversionService.class));
	}

	// Register a default embedded value resolver if no bean post-processor
	// (such as a PropertyPlaceholderConfigurer bean) registered any before:
	// at this point, primarily for resolution in annotation attribute values.
	if (!beanFactory.hasEmbeddedValueResolver()) {
		beanFactory.addEmbeddedValueResolver(strVal -> getEnvironment().resolvePlaceholders(strVal));
	}

	// Initialize LoadTimeWeaverAware beans early to allow for registering their transformers early.
	String[] weaverAwareNames = beanFactory.getBeanNamesForType(LoadTimeWeaverAware.class, false, false);
	for (String weaverAwareName : weaverAwareNames) {
		getBean(weaverAwareName);
	}

	// Stop using the temporary ClassLoader for type matching.
	beanFactory.setTempClassLoader(null);

	// Allow for caching all bean definition metadata, not expecting further changes.
	beanFactory.freezeConfiguration();

	// Instantiate all remaining (non-lazy-init) singletons.
	beanFactory.preInstantiateSingletons();
}

–>> preInstantiateSingletons()
在preInstantiateSingletons依次取出从xml解析的beanName,根据beanName从mergedBeanDefinitions获取该beanName对应的BeanDefinition,再判断该bean是否是抽象类对象、是否是单例对象、是否是懒加载,如果是懒加载则跳过实例化,在后面获取bean的时候再进行实例化,再判断该bean是否是FactoryBean工厂bean,由于User类不是工厂类,因此直接调用getBean(beanName),再调用AbstractBeanFactory.doGetBean()方法完成真正的获取bean对象过程。

@Override
public void preInstantiateSingletons() throws BeansException {
	if (logger.isTraceEnabled()) {
		logger.trace("Pre-instantiating singletons in " + this);
	}

	// Iterate over a copy to allow for init methods which in turn register new bean definitions.
	// While this may not be part of the regular factory bootstrap, it does otherwise work fine.
	List<String> beanNames = new ArrayList<>(this.beanDefinitionNames);

	// Trigger initialization of all non-lazy singleton beans...
	for (String beanName : beanNames) {
		RootBeanDefinition bd = getMergedLocalBeanDefinition(beanName);
		if (!bd.isAbstract() && bd.isSingleton() && !bd.isLazyInit()) {
		……
		}
	}
}

doGetBean()
在doGetBean()中会经过一系列判断最终来到是否单例判断这里,在方法内调用了getSingleton()方法,并在获取单例对象前通过createBean()创建了bean并进行初始化赋值

protected <T> T doGetBean(final String name, @Nullable final Class<T> requiredType,
		@Nullable final Object[] args, boolean typeCheckOnly) throws BeansException {
	// Create bean instance.
	if (mbd.isSingleton()) {
		sharedInstance = getSingleton(beanName, () -> {
			try {
				return createBean(beanName, mbd, args);
			}
			catch (BeansException ex) {
				// Explicitly remove instance from singleton cache: It might have been put there
				// eagerly by the creation process, to allow for circular reference resolution.
				// Also remove any beans that received a temporary reference to the bean.
				destroySingleton(beanName);
				throw ex;
			}
		});
		bean = getObjectForBeanInstance(sharedInstance, name, beanName, mbd);
	}
}

getSingleton()

public Object getSingleton(String beanName, ObjectFactory<?> singletonFactory) {
	Assert.notNull(beanName, "Bean name must not be null");
	synchronized (this.singletonObjects) {
		Object singletonObject = this.singletonObjects.get(beanName);
		if (singletonObject == null) {
			if (this.singletonsCurrentlyInDestruction) {
				throw new BeanCreationNotAllowedException(beanName,
						"Singleton bean creation not allowed while singletons of this factory are in destruction " +
						"(Do not request a bean from a BeanFactory in a destroy method implementation!)");
			}
			if (logger.isDebugEnabled()) {
				logger.debug("Creating shared instance of singleton bean '" + beanName + "'");
			}
			beforeSingletonCreation(beanName);
			boolean newSingleton = false;
			boolean recordSuppressedExceptions = (this.suppressedExceptions == null);
			if (recordSuppressedExceptions) {
				this.suppressedExceptions = new LinkedHashSet<>();
			}
			try {
				singletonObject = singletonFactory.getObject();
				newSingleton = true;
			}
			catch (IllegalStateException ex) {
				// Has the singleton object implicitly appeared in the meantime ->
				// if yes, proceed with it since the exception indicates that state.
				singletonObject = this.singletonObjects.get(beanName);
				if (singletonObject == null) {
					throw ex;
				}
			}
			catch (BeanCreationException ex) {
				if (recordSuppressedExceptions) {
					for (Exception suppressedException : this.suppressedExceptions) {
						ex.addRelatedCause(suppressedException);
					}
				}
				throw ex;
			}
			finally {
				if (recordSuppressedExceptions) {
					this.suppressedExceptions = null;
				}
				afterSingletonCreation(beanName);
			}
			if (newSingleton) {
				addSingleton(beanName, singletonObject);
			}
		}
		return singletonObject;
	}
}

1.先从beanFactory的singletonObjects中获取,如果结果不为空,返回结果,如果为空向下执行
2.执行singletonObject = singletonFactory.getObject()获取bean实例化对象,并将newSingleton设置为true表示新创建的单例对象
3.最后根据newSingleton标志位将新的单例对象添加进beanFactory的singletonObjects和registeredSingletons中

protected void addSingleton(String beanName, Object singletonObject) {
	synchronized (this.singletonObjects) {
		this.singletonObjects.put(beanName, singletonObject);
		this.singletonFactories.remove(beanName);
		this.earlySingletonObjects.remove(beanName);
		this.registeredSingletons.add(beanName);
	}
}

未完…
–>Bean的创建
–>Bean的获取
–>如何解决循环依赖问题

Bean 常见问题及解决办法如下: ### Bean 中使用多 Bean 的问题及解决办法 在 Bean 中使用多 Bean 时,由于 Bean 只会创建一次,直接使用多 Bean 无法达到每次使用时都获取新实的效果。可以通过以下三种方式解决:可参考案源码,链接为:https://pan.baidu.com/s/1p6rcfKOeWQIVkuhVybzZmQ ,提取码:zr99 [^1]。 ### Bean 的多线程并发安全问题及解决办法 在 Spring 框架里, Bean 是常见的 Bean 作用域型,但在多线程场景下可能产生并发安全问题。解决办法如下: - **同步机制**:通过对象的锁机制保证同一时间只有一个线程访问变量。过使用同步机制要求程序缜密地分析变量读写、对象锁定和释放等繁杂问题,程序设计和编写难度相对较大 [^4]。 - **ThreadLocal**:为每一个线程提供一个独立的变量副本,从而隔离多个线程对数据的访问冲突。同线程只操作自己线程的副本变量,提供了线程安全的共享对象。可以把安全的变量封装进 ThreadLocal [^4]。 ```java private static ThreadLocal<Integer> content = new ThreadLocal<Integer>() { protected Integer initialValue() { return (int) (Math.random() * 10 + 100); } }; private static ThreadLocal<Integer> test = new ThreadLocal<Integer>() { protected Integer initialValue() { return (int) (Math.random() * 10 + 100); } }; public Object get() { System.out.println(content.get()); System.out.println(test.get()); System.out.println(); return test.get(); } ``` - **改变 Bean 作用域**:将有状态的 Bean 的作用域由“singleton”改为“prototype”,如使用注解 `@Scope("prototype")` [^4]。 ### Bean 创建过程中的循环引用问题及解决办法 在 Bean 创建过程中,当满足、允许循环依赖且当前 Bean 正在创建中这些条件时,会提前曝光 `beanName` 的 `ObjectFactory` 用于解决循环引用。在 `doCreateBean` 方法中,创建完 Bean后,会调用 `addSingletonFactory` 方法,并重写 `getObject` 方法 [^3]。 ```java protected Object doCreateBean(final String beanName, final RootBeanDefinition mbd, final Object[] args) { // 创建bean instanceWrapper = createBeanInstance(beanName, mbd, args); // 判断是否需要提早曝光实 && 允许循环依赖 && 当前bean正在创建中 boolean earlySingletonExposure = (mbd.isSingleton() && this.allowCircularReferences && isSingletonCurrentlyInCreation(beanName)); if (earlySingletonExposure) { if (logger.isDebugEnabled()) { logger.debug("Eagerly caching bean '" + beanName + "' to allow for resolving potential circular references"); } // 提前曝光beanName的ObjectFactory,用于解决循环引用 addSingletonFactory(beanName, new ObjectFactory<Object>() { @Override public Object getObject() throws BeansException { // 应用后置处理器SmartInstantiationAwareBeanPostProcessor,允许返回指定bean的早期引用,若没有则直接返回bean return getEarlyBeanReference(beanName, mbd, bean); } }); } // 省略 } ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值