注意:这里是
FactoryBean
,而不是BeanFactory
html
FactoryBean
是一个工厂Bean
,用于生成某一个类型Bean
实例BeanFactory
是Spring
容器中的一个基本类也是很重要的一个类,用于建立和管理Spring
容器中的Bean
FactoryBean
首先它是一个Bean
,但又不单单是一个Bean
。它是一个能生产或修饰对象生成的工厂Bean
,相似于设计模式中的工厂模式和装饰器模式。它能在须要的时候生产一个对象,且不单单限于它自身,它能返回任何Bean
的实例。源码以下:java
public interface FactoryBean<T> {
String OBJECT_TYPE_ATTRIBUTE = "factoryBeanObjectType";
// 返回一个对象实例,这个对象会添加到容器中
@Nullable
T getObject() throws Exception;
// Bean的类型
@Nullable
Class<?> getObjectType();
// 控制是不是单例,返回true为单例(容器中保存一份),返回false为多例(每次获取调用getObject()建立新的)
default boolean isSingleton() {
return true;
}
}
复制代码
在
FactoryBean
接口中,有三个方法,使用的时候经过调用工厂Bean
获取FactoryBean
的getObject
方法建立对象:spring
getObject()
:返回一个对象实例,这个对象会添加到容器中getObjectType()
:获取Bean
的类型isSingleton()
:控制是不是单例,返回true为单例(容器中保存一份),返回false为多例(每次获取调用getObject()
建立新的)
FactoryBean
做为一个生产或修饰对象的工厂Bean
,那是如何生产Bean
的呢,我们经过实例来进行分析,这里就使用工厂Bean
来生产Color
对象设计模式
// 启动类
public class MainTest {
@Test
public void TestMain(){
AnnotationConfigApplicationContext applicationContext = new AnnotationConfigApplicationContext(AppConfig.class);
String[] beanNames = applicationContext.getBeanDefinitionNames();
for (String beanName : beanNames) {
System.out.println(beanName);
}
// 工厂Bean获取的是getObject建立的对象
Object factoryBean = applicationContext.getBean("colorFactoryBean");
System.out.println("Bean的类型" + factoryBean.getClass());
// 测试isSingleton控制单例多例
Object factoryBean2 = applicationContext.getBean("colorFactoryBean");
System.out.println("Bean的类型" + factoryBean.getClass());
System.out.println(factoryBean == factoryBean2);
// 经过加“&”获取ColorFactoryBean对象
Object factoryBean3 = applicationContext.getBean("&colorFactoryBean");
System.out.println(factoryBean3.getClass());
}
}
// 待生产的Color对象
public class Color {
}
// 建立一个spring定义的工厂Bean
public class ColorFactoryBean implements FactoryBean {
// 返回一个color对象,这个对象会添加到容器中
public Object getObject() throws Exception {
return new Color();
}
// Bean的类型
public Class<?> getObjectType() {
return Color.class;
}
// 控制是不是单例,返回true为单例(容器中保存一份),返回false为多例(每次获取调用getObject()建立新的)
public boolean isSingleton() {
return false;
}
}
// 配置类
@Configuration
public class AppConfig {
/** * 1.默认获取的是工厂Bean调用getObject建立的对象 * 2.要获取工厂Bean自己,须要给ID前面加一个“&” */
@Bean
public ColorFactoryBean colorFactoryBean(){
return new ColorFactoryBean();
}
}
复制代码
运行启动类,能够看到,已经将Bean对象给生产出来了,根据打印信息,能够得出如下结论:缓存
Bean
获取的是getObject
所建立的对象,这也就是所谓的生产Bean
isSingleton
方法返回值能够改变建立Bean
的单例仍是多例FactoryBean
自己注入进spring
容器中,获取的时候须要给ID前面加一个“&”参考:www.cnblogs.com/guitu18/p/1…markdown
FactoryBean
是怎么让Spring
容器管理调用它的getObject
所生成的Bean
的,我们经过源码来看看FactorBean
是如何生产Bean
的,app
在启动类中经过调用:AnnotationConfigApplicationContext
——> refresh()
方法——> getBean()
方法,再到AbstractBeanFactory
实现类,在这个类中,又调用了doGetBean
方法,doGetBean
能够说是Spring
容器中一个很核心的一个类,里面的功能不少很复杂,咱们在这篇文章中只关注和FactoryBean
相关的内容。截取部分代码:oop
【1】doGetBean
方法中调用getSingleton
方法 从Spring容器中获取单例Beanpost
protected <T> T doGetBean(String name, @Nullable Class<T> requiredType, @Nullable Object[] args, boolean typeCheckOnly) throws BeansException {
String beanName = this.transformedBeanName(name);
// 调用getSingleton方法 从Spring容器中获取单例Bean
Object sharedInstance = this.getSingleton(beanName);
Object bean;
if (sharedInstance != null && args == null) {
if (this.logger.isTraceEnabled()) {
if (this.isSingletonCurrentlyInCreation(beanName)) {
this.logger.trace("Returning eagerly cached instance of singleton bean '" + beanName + "' that is not fully initialized yet - a consequence of a circular reference");
} else {
this.logger.trace("Returning cached instance of singleton bean '" + beanName + "'");
}
}
bean = this.getObjectForBeanInstance(sharedInstance, name, beanName, (RootBeanDefinition)null);
}
....
}
复制代码
getSingleton
从Spring容器中获取单例Bean性能
@Nullable
public Object getSingleton(String beanName) {
return this.getSingleton(beanName, true);
}
@Nullable
protected Object getSingleton(String beanName, boolean allowEarlyReference) {
// 先从singletonObjects中获取单例Bean singletonObjects是一个ConcurrentHashMap
// key是beanName value是单例Bean
Object singletonObject = this.singletonObjects.get(beanName);
// 若是没有获取到,则判断是否是当前在建立中的单例Bean
if (singletonObject == null && this.isSingletonCurrentlyInCreation(beanName)) {
singletonObject = this.earlySingletonObjects.get(beanName);
if (singletonObject == null && allowEarlyReference) {
synchronized(this.singletonObjects) {
singletonObject = this.singletonObjects.get(beanName);
if (singletonObject == null) {
singletonObject = this.earlySingletonObjects.get(beanName);
if (singletonObject == null) {
ObjectFactory<?> singletonFactory = (ObjectFactory)this.singletonFactories.get(beanName);
if (singletonFactory != null) {
singletonObject = singletonFactory.getObject();
this.earlySingletonObjects.put(beanName, singletonObject);
this.singletonFactories.remove(beanName);
}
}
}
}
}
}
return singletonObject;
}
复制代码
【2】doGetBean
方法中调用getObjectForBeanInstance
,关键代码就从这里开始,查看源码:
protected Object getObjectForBeanInstance(Object beanInstance, String name, String beanName, @Nullable RootBeanDefinition mbd) {
// 这里判断 name是否是以&开头,不是通过处理的beanName 而且这个bean实例 不是FactoryBean类型的
// 若是是&开头而且不是FactoryBean类型 则抛出异常
if (BeanFactoryUtils.isFactoryDereference(name)) {
if (beanInstance instanceof NullBean) {
return beanInstance;
// 不是FactoryBean类型 或者name以&开头 直接返回bean实例,要根据beanName获取真正的FactoryBean实例的时候,在beanName前面加上&
} else if (!(beanInstance instanceof FactoryBean)) {
throw new BeanIsNotAFactoryException(beanName, beanInstance.getClass());
} else {
if (mbd != null) {
mbd.isFactoryBean = true;
}
return beanInstance;
}
} else if (!(beanInstance instanceof FactoryBean)) {
return beanInstance;
} else {
Object object = null;
if (mbd != null) {
mbd.isFactoryBean = true;
} else {
// factoryBeanObjectCache 看看是否是在缓存中存在
object = this.getCachedObjectForFactoryBean(beanName);
}
// 若是没有
if (object == null) {
// 若是能走到这里来 这个bean实例是FactoryBean类型的
FactoryBean<?> factory = (FactoryBean)beanInstance;
if (mbd == null && this.containsBeanDefinition(beanName)) {
mbd = this.getMergedLocalBeanDefinition(beanName);
}
boolean synthetic = mbd != null && mbd.isSynthetic();
//从这个方法的名字咱们能够看到这个方法的意思是:从FactoryBean中获取对象
object = this.getObjectFromFactoryBean(factory, beanName, !synthetic);
}
return object;
}
}
复制代码
分析以下:
- 第一个判断
BeanFactoryUtils.isFactoryDereference
:判断name是否不为空且以&
开头,若是是&开头而且不是FactoryBean类型 则抛出异常- 后面的判断
beanInstance instanceof FactoryBean
:不是FactoryBean
类型 或者name以&开头 直接返回bean实例,要根据beanName获取真正的FactoryBean
实例的时候,在beanName前面加上&
public static boolean isFactoryDereference(@Nullable String name) {
return name != null && name.startsWith("&");
}
复制代码
若是beanInstance不属于FactoryBean或其子类的实例,或者name是以&
开头就直接返回实例对象beanInstance,不然进入到if分支中。在if分支里的各类if .. ==null
判断是为了提升性能,我们只挑关键部分看:object = this.getObjectFromFactoryBean(factory, beanName, !synthetic);
继续跟踪进去看代码。
【3】getObjectFromFactoryBean
调用doGetObjectFromFactoryBean
方法
protected Object getObjectFromFactoryBean(FactoryBean<?> factory, String beanName, boolean shouldPostProcess) {
// FactoryBean类型的实例 调用isSingleton方法返回的是true,所传入的bean实例也要求是单例类型的
if (factory.isSingleton() && this.containsSingleton(beanName)) {
synchronized(this.getSingletonMutex()) {
Object object = this.factoryBeanObjectCache.get(beanName);
if (object == null) {
// 调用doGetObjectFromFactoryBean方法从FactoryBean中获取bean对象,这里是调用的FactoryBean的getObject方法来获取的
object = this.doGetObjectFromFactoryBean(factory, beanName);
// 再从缓存中获取一次
Object alreadyThere = this.factoryBeanObjectCache.get(beanName);
// 若是上一步的缓存中获取到了则用缓存中的替代咱们从FactoryBean中获取的bean
if (alreadyThere != null) {
object = alreadyThere;
} else {
if (shouldPostProcess) {
if (this.isSingletonCurrentlyInCreation(beanName)) {
return object;
}
this.beforeSingletonCreation(beanName);
try {
object = this.postProcessObjectFromFactoryBean(object, beanName);
} catch (Throwable var14) {
throw new BeanCreationException(beanName, "Post-processing of FactoryBean's singleton object failed", var14);
} finally {
this.afterSingletonCreation(beanName);
}
}
if (this.containsSingleton(beanName)) {
this.factoryBeanObjectCache.put(beanName, object);
}
}
}
return object;
}
} else {
Object object = this.doGetObjectFromFactoryBean(factory, beanName);
if (shouldPostProcess) {
try {
object = this.postProcessObjectFromFactoryBean(object, beanName);
} catch (Throwable var17) {
throw new BeanCreationException(beanName, "Post-processing of FactoryBean's object failed", var17);
}
}
return object;
}
}
复制代码
分析:
factory.isSingleton() && this.containsSingleton(beanName)
判断就是调用isSingleton方法返回的是true,也就是对用实例中经过isSingleton
方法返回true来控制单例this.doGetObjectFromFactoryBean(factory, beanName)
:调用doGetObjectFromFactoryBean
方法从FactoryBean
中获取bean对象,这里是调用的FactoryBean
的getObject方法来获取的
【4】调用doGetObjectFromFactoryBean
方法
private Object doGetObjectFromFactoryBean(FactoryBean<?> factory, String beanName) throws BeanCreationException {
Object object;
try {
if (System.getSecurityManager() != null) {
AccessControlContext acc = this.getAccessControlContext();
try {
object = AccessController.doPrivileged(factory::getObject, acc);
} catch (PrivilegedActionException var6) {
throw var6.getException();
}
} else {
object = factory.getObject();
}
} catch (FactoryBeanNotInitializedException var7) {
throw new BeanCurrentlyInCreationException(beanName, var7.toString());
} catch (Throwable var8) {
throw new BeanCreationException(beanName, "FactoryBean threw exception on object creation", var8);
}
if (object == null) {
if (this.isSingletonCurrentlyInCreation(beanName)) {
throw new BeanCurrentlyInCreationException(beanName, "FactoryBean which is currently in creation returned null from getObject");
}
object = new NullBean();
}
return object;
}
复制代码
分析:
- object = factory.getObject():这个factory就是咱们传入的
beanInstance
实例。绕了这么一大圈,getBean方法返回的竟然是咱们实现FactoryBean接口定义的getObject方法
到这里,就证明了案例中的结论了:FactoryBean是一个能生产或修饰对象生成的工厂Bean。一个Bean若是实现了FactoryBean接口,那么根据该Bean的名称获取到的其实是getObject()返回的对象,而不是这个Bean自身实例,若是要获取这个Bean自身实例,那么须要在名称前面加上'&'符号。