亚洲乱码中文字幕综合,中国熟女仑乱hd,亚洲精品乱拍国产一区二区三区,一本大道卡一卡二卡三乱码全集资源,又粗又黄又硬又爽的免费视频

基于springboot bean的實(shí)例化過(guò)程和屬性注入過(guò)程

 更新時(shí)間:2021年11月17日 14:55:05   作者:leileibest_437147623  
這篇文章主要介紹了基于springboot bean的實(shí)例化過(guò)程和屬性注入過(guò)程,具有很好的參考價(jià)值,希望對(duì)大家有所幫助。如有錯(cuò)誤或未考慮完全的地方,望不吝賜教

bean的實(shí)例化過(guò)程和屬性注入過(guò)程

了解過(guò)springboot的加載流程的都知道springboot初始化bean都在refresh方法中。

這個(gè)方法代碼如下:

// Prepare this context for refreshing.
prepareRefresh();
// Tell the subclass to refresh the internal bean factory.新建beanFactory
ConfigurableListableBeanFactory beanFactory = obtainFreshBeanFactory();
// Prepare the bean factory for use in this context.
prepareBeanFactory(beanFactory);
try {
   // Allows post-processing of the bean factory in context subclasses.
   postProcessBeanFactory(beanFactory);
   // Invoke factory processors registered as beans in the context.
   // 加載實(shí)現(xiàn)beanFactoryPostProcessor的bean,bean定義的時(shí)候執(zhí)行
   invokeBeanFactoryPostProcessors(beanFactory);
   // Register bean processors that intercept bean creation.
   // 加載實(shí)現(xiàn)了beanPostProcessor,在bean實(shí)例化前、后執(zhí)行
   registerBeanPostProcessors(beanFactory);
   // Initialize message source for this context.
   initMessageSource();
   // Initialize event multicaster for this context.
   initApplicationEventMulticaster();
   // Initialize other special beans in specific context subclasses.
   onRefresh();
   // Check for listener beans and register them.
   registerListeners();
   // Instantiate all remaining (non-lazy-init) singletons.
   //實(shí)例化非懶加載的bean、bean封裝、屬性注入、注解注入(主要使用BeanPostProcessor或子類實(shí)現(xiàn))等
   finishBeanFactoryInitialization(beanFactory);
   // Last step: publish corresponding event.
   finishRefresh();

這里我們主要看下finishBeanfactoryInitialization方法。此方法實(shí)現(xiàn)了bean的實(shí)例和屬性注入等。進(jìn)入此方法的最后一行。

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

注釋寫的很清楚,實(shí)例化剩余非懶加載的bean。此方法的實(shí)現(xiàn)是核心類DefaultLisListableBeanFactory實(shí)現(xiàn)。這個(gè)方法中有個(gè)判斷:bean是否是beanFactory的實(shí)現(xiàn)類。

如果是則獲取bean的時(shí)候會(huì)從beanFactory實(shí)現(xiàn)類的getObject中獲取,我們重點(diǎn)看看getBean這個(gè)方法。

getBean是spring中最重要、最牛逼的方法之一,具體的邏輯是通過(guò)doGetBean方法處理的。

我們看下doGetBean方法,方法很長(zhǎng)。我們分成幾個(gè)部分去看。

1、先判斷是否已經(jīng)存在緩存中,代碼如下:

if (sharedInstance != null && args == null) {
   if (logger.isDebugEnabled()) {
      if (isSingletonCurrentlyInCreation(beanName)) {
         logger.debug("Returning eagerly cached instance of singleton bean '" + beanName +
               "' that is not fully initialized yet - a consequence of a circular reference");
      }
      else {
         logger.debug("Returning cached instance of singleton bean '" + beanName + "'");
      }
   }
   bean = getObjectForBeanInstance(sharedInstance, name, beanName, null);

2、從父beanfactory中獲取

BeanFactory parentBeanFactory = getParentBeanFactory();
if (parentBeanFactory != null && !containsBeanDefinition(beanName)) {
   // Not found -> check parent.
   String nameToLookup = originalBeanName(name);
   if (parentBeanFactory instanceof AbstractBeanFactory) {
      return ((AbstractBeanFactory) parentBeanFactory).doGetBean(
            nameToLookup, requiredType, args, typeCheckOnly);
   }
   else if (args != null) {
      // Delegation to parent with explicit args.
      return (T) parentBeanFactory.getBean(nameToLookup, args);
   }
   else {
      // No args -> delegate to standard getBean method.
      return parentBeanFactory.getBean(nameToLookup, requiredType);
   }
}

3、直接創(chuàng)建RootBeanDefinition

//mark 給此bean 馬克一下。防止重復(fù)創(chuàng)建
if (!typeCheckOnly) {
   markBeanAsCreated(beanName);
}
try {
   final RootBeanDefinition mbd = getMergedLocalBeanDefinition(beanName);
   checkMergedBeanDefinition(mbd, beanName, args);
   // Guarantee initialization of beans that the current bean depends on.
   String[] dependsOn = mbd.getDependsOn();
   if (dependsOn != null) {
      for (String dep : dependsOn) {
         if (isDependent(beanName, dep)) {
            throw new BeanCreationException(mbd.getResourceDescription(), beanName,
                  "Circular depends-on relationship between '" + beanName + "' and '" + dep + "'");
         }
         registerDependentBean(dep, beanName);
         getBean(dep);
      }
   }

4、是singleton還是prototype類型的,根據(jù)不同類型去實(shí)例化bean,代碼只貼了單例的類型:

// 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);

5、檢查bean的類型是否匹配

// Check if required type matches the type of the actual bean instance.
if (requiredType != null && !requiredType.isInstance(bean)) {
   try {
      T convertedBean = getTypeConverter().convertIfNecessary(bean, requiredType);
      if (convertedBean == null) {
         throw new BeanNotOfRequiredTypeException(name, requiredType, bean.getClass());
      }
      return convertedBean;
   }
   catch (TypeMismatchException ex) {
      if (logger.isDebugEnabled()) {
         logger.debug("Failed to convert bean '" + name + "' to required type '" +
               ClassUtils.getQualifiedName(requiredType) + "'", ex);
      }
      throw new BeanNotOfRequiredTypeException(name, requiredType, bean.getClass());
   }
}

整個(gè)doGetBean方法改成這5個(gè)部分,重點(diǎn)看下第4個(gè)部分中的createBean和getObjectForBeanInstance方法。

1、createBean方法,里面主要是2個(gè)部分,bean直接是通過(guò)BeanPostProcessor的postProcessBeforeIntantiation方法獲取的。

注釋也是描述的很清楚:Give BeanPostProcessors a chance to return a proxy instead of the bean instance(英語(yǔ)渣渣不敢瞎翻譯誤導(dǎo)大家,理解就好)

代碼如下:

try {
   // Give BeanPostProcessors a chance to return a proxy instead of the target bean instance.
   Object bean = resolveBeforeInstantiation(beanName, mbdToUse);
   if (bean != null) {
      return bean;
   }
}
catch (Throwable ex) {
   throw new BeanCreationException(mbdToUse.getResourceDescription(), beanName,
         "BeanPostProcessor before instantiation of bean failed", ex);
}

第一個(gè)部分自己實(shí)現(xiàn),那么createBean方法第2個(gè)部分毋庸置疑肯定是spring去實(shí)例化bean,代碼如下:

try {
   Object beanInstance = doCreateBean(beanName, mbdToUse, args);
   if (logger.isDebugEnabled()) {
      logger.debug("Finished creating instance of bean '" + beanName + "'");
   }
   return beanInstance;
}

又是do開頭的方法,說(shuō)明這個(gè)也是一個(gè)創(chuàng)建方法,spring中一般do開頭的都是用于創(chuàng)建某個(gè)對(duì)象。跟著代碼走,看下doCreateBean方法,在查看此方法之前,可能需要了解下BeanWarpper這個(gè)封裝類。bean的封裝、屬性注入等都是用BeanWarpper去完成的。

看下代碼:

// Instantiate the bean.
BeanWrapper instanceWrapper = null;
if (mbd.isSingleton()) {
   instanceWrapper = this.factoryBeanInstanceCache.remove(beanName);
}
if (instanceWrapper == null) {
   instanceWrapper = createBeanInstance(beanName, mbd, args);
}

進(jìn)入createBeanInstance方法中,就是調(diào)用構(gòu)造器去實(shí)例化bean,返回beanWrapper。通過(guò)構(gòu)造器獲取實(shí)例代碼如下:

// Need to determine the constructor...
Constructor<?>[] ctors = determineConstructorsFromBeanPostProcessors(beanClass, beanName);
if (ctors != null ||
      mbd.getResolvedAutowireMode() == RootBeanDefinition.AUTOWIRE_CONSTRUCTOR ||
      mbd.hasConstructorArgumentValues() || !ObjectUtils.isEmpty(args))  {
   return autowireConstructor(beanName, mbd, ctors, args);
}
// No special handling: simply use no-arg constructor.
return instantiateBean(beanName, mbd);

這里實(shí)例化我一開始以為就是簡(jiǎn)單的反射,后面我點(diǎn)進(jìn)去時(shí)候發(fā)現(xiàn)里面一直提策略實(shí)例化,我目前了解的是可以解決Override的問(wèn)題等。如果有興趣的可以自行查看。到這里為止。我們終于實(shí)例化bean了。下面看下第二步bean的屬性注入等。

代碼如下:

Object exposedObject = bean;
try {
   populateBean(beanName, mbd, instanceWrapper);
   exposedObject = initializeBean(beanName, exposedObject, mbd);
}
catch (Throwable ex) {
   if (ex instanceof BeanCreationException && beanName.equals(((BeanCreationException) ex).getBeanName())) {
      throw (BeanCreationException) ex;
   }
   else {
      throw new BeanCreationException(
            mbd.getResourceDescription(), beanName, "Initialization of bean failed", ex);
   }
}

populateBean方法名稱就暴露他是干啥的:填充bean。我放一段比較重要的部分:

if (hasInstAwareBpps || needsDepCheck) {
   if (pvs == null) {
      pvs = mbd.getPropertyValues();
   }
   PropertyDescriptor[] filteredPds = filterPropertyDescriptorsForDependencyCheck(bw, mbd.allowCaching);
   if (hasInstAwareBpps) {
      for (BeanPostProcessor bp : getBeanPostProcessors()) {
         if (bp instanceof InstantiationAwareBeanPostProcessor) {
            InstantiationAwareBeanPostProcessor ibp = (InstantiationAwareBeanPostProcessor) bp;
            pvs = ibp.postProcessPropertyValues(pvs, filteredPds, bw.getWrappedInstance(), beanName);
            if (pvs == null) {
               return;
            }
         }
      }
   }
   if (needsDepCheck) {
      checkDependencies(beanName, mbd, filteredPds, pvs);
   }
}

這段代碼貌似沒(méi)有什么注入、填充什么的,我們看下InstantiationAwareBeanPostProcessor這個(gè)接口,發(fā)現(xiàn)這個(gè)接口有個(gè)很熟悉的實(shí)現(xiàn)類是:AutowiredAnnotationBeanPostProcessor。這個(gè)類的方法中我們看到終于看到了jnject方法。但是在inject之前需要調(diào)用下findAutowiringMatedata方法獲取一下元數(shù)據(jù):

// Fall back to class name as cache key, for backwards compatibility with custom callers.
String cacheKey = (StringUtils.hasLength(beanName) ? beanName : clazz.getName());
// Quick check on the concurrent map first, with minimal locking.
InjectionMetadata metadata = this.injectionMetadataCache.get(cacheKey);
if (InjectionMetadata.needsRefresh(metadata, clazz)) {
   synchronized (this.injectionMetadataCache) {
      metadata = this.injectionMetadataCache.get(cacheKey);
      if (InjectionMetadata.needsRefresh(metadata, clazz)) {
         if (metadata != null) {
            metadata.clear(pvs);
         }
         metadata = buildAutowiringMetadata(clazz);
         this.injectionMetadataCache.put(cacheKey, metadata);
      }
   }
} 
return metadata;

那么問(wèn)題又來(lái)了,這個(gè)injectionMetadataCache集合值是從那里來(lái)的呢?AutowiredAnnotationBeanPostProcessor實(shí)現(xiàn)了MergeBeandefinitionPostProcessor,那么就好了,肯定是在bean實(shí)例的時(shí)候調(diào)用了postProcessMergedBeanDefintion這個(gè)方法。

果然在doCreateBean方法中有這么一段:

// Allow post-processors to modify the merged bean definition.
synchronized (mbd.postProcessingLock) {
   if (!mbd.postProcessed) {
      try {
         //通過(guò) BeanPostProcessor將需要注解的元數(shù)據(jù) 放到Map中
         applyMergedBeanDefinitionPostProcessors(mbd, beanType, beanName);
      }
      catch (Throwable ex) {
         throw new BeanCreationException(mbd.getResourceDescription(), beanName,
               "Post-processing of merged bean definition failed", ex);
      }
      mbd.postProcessed = true;
   }
}

哎,spring縝密啊。元數(shù)據(jù)有了,下面我們看下element.inject()方法是如何操作的:

if (this.isField) {
   Field field = (Field) this.member;
   ReflectionUtils.makeAccessible(field);
   field.set(target, getResourceToInject(target, requestingBeanName));
}
else {
   if (checkPropertySkipping(pvs)) {
      return;
   }
   try {
      Method method = (Method) this.member;
      ReflectionUtils.makeAccessible(method);
      method.invoke(target, getResourceToInject(target, requestingBeanName));
   }
   catch (InvocationTargetException ex) {
      throw ex.getTargetException();
   }
}

方法簡(jiǎn)單明了,直接使用反射將值set到屬性中,至此 bean的實(shí)例、屬性注入基本完成,下面我們回頭來(lái)看doGetBean的另一個(gè)方法getObjectForBeanInstance。

2、getObjectForBeanInstance方法。對(duì)于是FactoryBean類型的 bean通過(guò)getObject獲取到bean的代理實(shí)例,跟著方法一直走下去會(huì)到getObejct()方法中。

if (System.getSecurityManager() != null) {
   AccessControlContext acc = getAccessControlContext();
   try {
      object = AccessController.doPrivileged((PrivilegedExceptionAction<Object>) factory::getObject, acc);
   }
   catch (PrivilegedActionException pae) {
      throw pae.getException();
   }
}
else {
   //從FactoryBean實(shí)現(xiàn)bean中g(shù)etObejct獲取到bean
   object = factory.getObject();
}

到此 finishBeanfactoryInitialization方法執(zhí)行結(jié)束!

bean實(shí)例化流程說(shuō)明

bean實(shí)例化流程流程是在onRefresh方法的finishBeanFactoryInitialization中。進(jìn)入該方法

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();
    }

1、beanFactory.freezeConfiguration(); 標(biāo)記正在實(shí)例化

當(dāng)前有183個(gè)bean正在實(shí)例化中。

2、調(diào)用beanFactory.preInstantiateSingletons(); 實(shí)例化bean

以上為個(gè)人經(jīng)驗(yàn),希望能給大家一個(gè)參考,也希望大家多多支持腳本之家。

相關(guān)文章

最新評(píng)論