最新国产好看的视频,伊人天堂AV在线,国产Aaaaaa视频,蜜臀视频在线观看一区,人妻av色图,密臀久久久精品影片,青青视频免费观看毛片,久草在线观看视,国产三级精品色情在线

淺談Spring IoC容器的依賴注入原理

 更新時(shí)間:2018年03月08日 09:08:52   作者:芥末無疆sss  
這篇文章主要介紹了淺談Spring IoC容器的依賴注入原理,小編覺得挺不錯(cuò)的,現(xiàn)在分享給大家,也給大家做個(gè)參考。一起跟隨小編過來看看吧

本文介紹了淺談Spring IoC容器的依賴注入原理,分享給大家,具體如下:

IoC容器初始化的過程,主要完成的工作是在IoC容器中建立 BeanDefinition 數(shù)據(jù)映射,并沒有看到IoC容器對(duì)Bean依賴關(guān)系進(jìn)行注入,

假設(shè)當(dāng)前IoC容器已經(jīng)載入用戶定義的Bean信息,依賴注入主要發(fā)生在兩個(gè)階段

正常情況下,由用戶第一次向IoC容器索要Bean時(shí)觸發(fā)

但我們可以在 BeanDefinition 信息中通過控制 lazy-init 屬性來讓容器完成對(duì)Bean的預(yù)實(shí)例化,即在初始化的過程中就完成某些Bean的依賴注入的過程

1.getBean觸發(fā)的依賴注入

在基本的IoC容器接口 BeanFactory 中,有一個(gè) getBean 的接口定義,這個(gè)接口的實(shí)現(xiàn)就是觸發(fā)依賴注入發(fā)生的地方.為了進(jìn)一步了解這個(gè)依賴注入的過程,我們從 DefaultListableBeanFactory 的基類 AbstractBeanFactory 入手去看看getBean的實(shí)現(xiàn)

// 這里是對(duì) BeanFactory 接口的實(shí)現(xiàn),比如getBean接口方法
  //這些getBean接口方法最終是通過調(diào)用doGetBean來實(shí)現(xiàn)的
  @Override
  public Object getBean(String name) throws BeansException {
    return doGetBean(name, null, null, false);
  }

  @Override
  public <T> T getBean(String name, Class<T> requiredType) throws BeansException {
    return doGetBean(name, requiredType, null, false);
  }

  @Override
  public Object getBean(String name, Object... args) throws BeansException {
    return doGetBean(name, null, args, false);
  }

  public <T> T getBean(String name, Class<T> requiredType, Object... args) throws BeansException {
    return doGetBean(name, requiredType, args, false);
  }

    //這里是實(shí)際取得Bean的地方,也就是觸發(fā)依賴注入發(fā)生的地方
  @SuppressWarnings("unchecked")
  protected <T> T doGetBean(
      final String name, final Class<T> requiredType, final Object[] args, boolean typeCheckOnly)
      throws BeansException {

    final String beanName = transformedBeanName(name);
    Object bean;

    // Eagerly check singleton cache for manually registered singletons.
        //急切地檢查單例人士緩存手動(dòng)注冊(cè)的單例
        //先從緩存中取得Bean,處理那些已經(jīng)被創(chuàng)建過的單例Bean,這種Bean不要重復(fù)創(chuàng)建
    Object sharedInstance = getSingleton(beanName);
    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 + "'");
        }
      }
            //這里的getObjectForBeanInstance完成的是FactoryBean的相關(guān)處理,以取得FactoryBean的相關(guān)處理,以取得FactoryBean的生產(chǎn)結(jié)果,BeanFactory和FactoryBean的區(qū)別已在前面講過,這個(gè)過程在后面還會(huì)詳細(xì)地分析
      bean = getObjectForBeanInstance(sharedInstance, name, beanName, null);
    }

    else {
      // Fail if we're already creating this bean instance:
      // We're assumably within a circular reference.
      if (isPrototypeCurrentlyInCreation(beanName)) {
        throw new BeanCurrentlyInCreationException(beanName);
      }

            // // 檢查IoC容器中的BeanDefinition是否存在,若在當(dāng)前工廠不存在則去順著雙親BeanFactory鏈一直向上找
      BeanFactory parentBeanFactory = getParentBeanFactory();
      if (parentBeanFactory != null && !containsBeanDefinition(beanName)) {
        // Not found -> check parent.
        String nameToLookup = originalBeanName(name);
        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);
        }
      }

      if (!typeCheckOnly) {
        markBeanAsCreated(beanName);
      }

      try {
                //根據(jù)Bean的名字取得BeanDefinition 
        final RootBeanDefinition mbd = getMergedLocalBeanDefinition(beanName);
        checkMergedBeanDefinition(mbd, beanName, args);

        // Guarantee initialization of beans that the current bean depends on.
                //遞歸獲得當(dāng)前Bean依賴的所有Bean(如果有的話)
        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);
          }
        }

                //通過調(diào)用createBean方法創(chuàng)建Singleton bean實(shí)例
        if (mbd.isSingleton()) {
          sharedInstance = getSingleton(beanName, new ObjectFactory<Object>() {
            @Override
            public Object getObject() throws BeansException {
              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);
        }
                //這里是創(chuàng)建prototype bean的地方
        else if (mbd.isPrototype()) {
          // It's a prototype -> create a new instance.
          Object prototypeInstance = null;
          try {
            beforePrototypeCreation(beanName);
            prototypeInstance = createBean(beanName, mbd, args);
          }
          finally {
            afterPrototypeCreation(beanName);
          }
          bean = getObjectForBeanInstance(prototypeInstance, name, beanName, mbd);
        }

        else {
          String scopeName = mbd.getScope();
          final Scope scope = this.scopes.get(scopeName);
          if (scope == null) {
            throw new IllegalStateException("No Scope registered for scope name '" + scopeName + "'");
          }
          try {
            Object scopedInstance = scope.get(beanName, new ObjectFactory<Object>() {
              @Override
              public Object getObject() throws BeansException {
                beforePrototypeCreation(beanName);
                try {
                  return createBean(beanName, mbd, args);
                }
                finally {
                  afterPrototypeCreation(beanName);
                }
              }
            });
            bean = getObjectForBeanInstance(scopedInstance, name, beanName, mbd);
          }
          catch (IllegalStateException ex) {
            throw new BeanCreationException(beanName,
                "Scope '" + scopeName + "' is not active for the current thread; consider " +
                "defining a scoped proxy for this bean if you intend to refer to it from a singleton",
                ex);
          }
        }
      }
      catch (BeansException ex) {
        cleanupAfterBeanCreationFailure(beanName);
        throw ex;
      }
    }

    // Check if required type matches the type of the actual bean instance.
        // 這里對(duì)創(chuàng)建的Bean進(jìn)行類型檢查,如果沒有問題,就返回這個(gè)新創(chuàng)建的Bean,這個(gè)Bean已經(jīng)是包含了依賴關(guān)系的Bean
    if (requiredType != null && bean != null && !requiredType.isAssignableFrom(bean.getClass())) {
      try {
        return getTypeConverter().convertIfNecessary(bean, requiredType);
      }
      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());
      }
    }
    return (T) bean;
  }

依賴注入就是在這里被觸發(fā)的.而依賴注入的發(fā)生是在容器中的BeanDefinition數(shù)據(jù)已經(jīng)建立好的前提下進(jìn)行的.雖然我們可以用最簡(jiǎn)單的方式來描述IoC容器,那就是視其為一個(gè)HashMap,但只能說這個(gè)HashMap是容器的最基本的數(shù)據(jù)結(jié)構(gòu),而不是IoC容器的全部.

關(guān)于這個(gè)依賴注入過程會(huì)在下面詳解,圖1.1可以看到依賴注入的大致過程.

圖1.1 依賴注入的過程

getBean是依賴注入的起點(diǎn),之后會(huì)調(diào)用AbstractAutowireCapableBeanFactory中的createBean來生產(chǎn)需要的Bean,還對(duì)Bean初始化進(jìn)行了處理,比如實(shí)現(xiàn)了在BeanDefinition中的init-method屬性定義,Bean后置處理器等.下面通過createBean代碼了解這個(gè)過程

@Override
  protected Object createBean(String beanName, RootBeanDefinition mbd, Object[] args) throws BeanCreationException {
    if (logger.isDebugEnabled()) {
      logger.debug("Creating instance of bean '" + beanName + "'");
    }
    RootBeanDefinition mbdToUse = mbd;

    // Make sure bean class is actually resolved at this point, and
    // clone the bean definition in case of a dynamically resolved Class
    // which cannot be stored in the shared merged bean definition.
        //這里判斷需要?jiǎng)?chuàng)建的Bean是否可以被實(shí)例化,這個(gè)類是否可以通過類加載器來載入
    Class<?> resolvedClass = resolveBeanClass(mbd, beanName);
    if (resolvedClass != null && !mbd.hasBeanClass() && mbd.getBeanClassName() != null) {
      mbdToUse = new RootBeanDefinition(mbd);
      mbdToUse.setBeanClass(resolvedClass);
    }

    // Prepare method overrides.
    try {
      mbdToUse.prepareMethodOverrides();
    }
    catch (BeanDefinitionValidationException ex) {
      throw new BeanDefinitionStoreException(mbdToUse.getResourceDescription(),
          beanName, "Validation of method overrides failed", ex);
    }

    try {
      // Give BeanPostProcessors a chance to return a proxy instead of the target bean instance.
            //如果Bean配置了PostProcessor,那么這里返回的是一個(gè)Proxy
      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);
    }

    try {
      Object beanInstance = doCreateBean(beanName, mbdToUse, args);
      if (logger.isDebugEnabled()) {
        logger.debug("Finished creating instance of bean '" + beanName + "'");
      }
      return beanInstance;
    }
    catch (BeanCreationException ex) {
      // A previously detected exception with proper bean creation context already...
      throw ex;
    }
    catch (ImplicitlyAppearedSingletonException ex) {
      // An IllegalStateException to be communicated up to DefaultSingletonBeanRegistry...
      throw ex;
    }
    catch (Throwable ex) {
      throw new BeanCreationException(
          mbdToUse.getResourceDescription(), beanName, "Unexpected exception during bean creation", ex);
    }
  }



  //接著到doCreate中去看看Bean是怎樣生成的
  protected Object doCreateBean(final String beanName, final RootBeanDefinition mbd, final Object[] args) {
    // Instantiate the bean.
        //用來持有創(chuàng)建出來的Bean對(duì)象
    BeanWrapper instanceWrapper = null;
        //如果是單例,則先把緩存中的同名Bean清除
    if (mbd.isSingleton()) {
      instanceWrapper = this.factoryBeanInstanceCache.remove(beanName);
    }
        //這里是創(chuàng)建Bean的地方,由createBeanInstance來完成
    if (instanceWrapper == null) {
            //根據(jù)指定bean使用對(duì)應(yīng)的策略創(chuàng)建新的實(shí)例,如:工廠方法,構(gòu)造函數(shù)自動(dòng)注入,簡(jiǎn)單初始化
      instanceWrapper = createBeanInstance(beanName, mbd, args);
    }
    final Object bean = (instanceWrapper != null ? instanceWrapper.getWrappedInstance() : null);
    Class<?> beanType = (instanceWrapper != null ? instanceWrapper.getWrappedClass() : null);

    // Allow post-processors to modify the merged bean definition.
    synchronized (mbd.postProcessingLock) {
      if (!mbd.postProcessed) {
        applyMergedBeanDefinitionPostProcessors(mbd, beanType, beanName);
        mbd.postProcessed = true;
      }
    }

    // Eagerly cache singletons to be able to resolve circular references
    // even when triggered by lifecycle interfaces like BeanFactoryAware.
        //是否需要提前曝光:單例&允許循環(huán)依賴&當(dāng)前bean正在創(chuàng)建中,檢測(cè)循環(huán)依賴
    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");
      }
            //為避免后期循環(huán)依賴,可以在bean初始化完成前將創(chuàng)建實(shí)例的ObjectFactory加入工廠
      addSingletonFactory(beanName, new ObjectFactory<Object>() {
        @Override
        public Object getObject() throws BeansException {
                    //對(duì)bean再次依賴引用,主要應(yīng)用SMartInstantialiationAware BeanPostProcessor,
                    //其中我們熟知的AOP就是在這里將advice動(dòng)態(tài)織入bean中,若無則直接返回bean,不做任何處理
          return getEarlyBeanReference(beanName, mbd, bean);
        }
      });
    }

    // Initialize the bean instance.
        //這里是對(duì)Bean的初始化,依賴注入往往在這里發(fā)生,這個(gè)exposedObject在初始化處理完后悔返回作為依賴注入完成后的Bean
    Object exposedObject = bean;
    try {
            //對(duì)bean進(jìn)行填充,將各個(gè)屬性值注入,其中可能存在依賴于其他bean的屬性,則會(huì)遞歸初始化依賴bean
      populateBean(beanName, mbd, instanceWrapper);
      if (exposedObject != null) {
                //調(diào)用初始化方法,比如init-method
        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);
      }
    }

    if (earlySingletonExposure) {
      Object earlySingletonReference = getSingleton(beanName, false);
            // earlySingletonReference 只有在檢測(cè)到有循環(huán)依賴的情況下才會(huì)非空
      if (earlySingletonReference != null) {
        if (exposedObject == bean) {
                    //如果exposedObject 沒有在初始化方法中被改變,也就是沒有被增強(qiáng)
          exposedObject = earlySingletonReference;
        }
        else if (!this.allowRawInjectionDespiteWrapping && hasDependentBean(beanName)) {
          String[] dependentBeans = getDependentBeans(beanName);
          Set<String> actualDependentBeans = new LinkedHashSet<String>(dependentBeans.length);
          for (String dependentBean : dependentBeans) {
                        //檢測(cè)依賴
            if (!removeSingletonIfCreatedForTypeCheckOnly(dependentBean)) {
              actualDependentBeans.add(dependentBean);
            }
          }
                    //因?yàn)閎ean創(chuàng)建后其所依賴的bean一定是已經(jīng)創(chuàng)建的,actualDependentBeans非空則表示當(dāng)前bean創(chuàng)建后其依賴的bean卻沒有全部創(chuàng)建完,也就是說存在循環(huán)依賴
          if (!actualDependentBeans.isEmpty()) {
            throw new BeanCurrentlyInCreationException(beanName,
                "Bean with name '" + beanName + "' has been injected into other beans [" +
                StringUtils.collectionToCommaDelimitedString(actualDependentBeans) +
                "] in its raw version as part of a circular reference, but has eventually been " +
                "wrapped. This means that said other beans do not use the final version of the " +
                "bean. This is often the result of over-eager type matching - consider using " +
                "'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example.");
          }
        }
      }
    }
      // Register bean as disposable.
    try {
            //根據(jù)scope注冊(cè)bean
      registerDisposableBeanIfNecessary(beanName, bean, mbd);
    }
    catch (BeanDefinitionValidationException ex) {
      throw new BeanCreationException(mbd.getResourceDescription(), beanName, "Invalid destruction signature", ex);
    }

    return exposedObject;
  }

依賴注入其實(shí)包括兩個(gè)主要過程

  1. 生產(chǎn)Bea所包含的Java對(duì)象
  2. Bean對(duì)象生成之后,把這些Bean對(duì)象的依賴關(guān)系設(shè)置好

我們從上可以看到與依賴注入關(guān)系特別密切的方法有

createBeanInstance
生成Bean包含的Java對(duì)象

populateBean.
處理對(duì)各種Bean對(duì)象的屬性進(jìn)行處理的過程(即依賴關(guān)系處理的過程)

先來看 createBeanInstance源碼

/**
   * Create a new instance for the specified bean, using an appropriate instantiation strategy:
   * factory method, constructor autowiring, or simple instantiation.
   * @param beanName the name of the bean
   * @param mbd the bean definition for the bean
   * @param args explicit arguments to use for constructor or factory method invocation
   * @return a BeanWrapper for the new instance
   */
  protected BeanWrapper createBeanInstance(String beanName, RootBeanDefinition mbd, Object[] args) {
    // Make sure bean class is actually resolved at this point.
        // 確認(rèn)需要?jiǎng)?chuàng)建的Bean實(shí)例的類可以實(shí)例化
    Class<?> beanClass = resolveBeanClass(mbd, beanName);

    if (beanClass != null && !Modifier.isPublic(beanClass.getModifiers()) && !mbd.isNonPublicAccessAllowed()) {
      throw new BeanCreationException(mbd.getResourceDescription(), beanName,
          "Bean class isn't public, and non-public access not allowed: " + beanClass.getName());
    }

    Supplier<?> instanceSupplier = mbd.getInstanceSupplier();
    if (instanceSupplier != null) {
      return obtainFromSupplier(instanceSupplier, beanName);
    }
        //若工廠方法非空,則使用工廠方法策略對(duì)Bean進(jìn)行實(shí)例化
    if (mbd.getFactoryMethodName() != null) {
      return instantiateUsingFactoryMethod(beanName, mbd, args);
    }

    // Shortcut when re-creating the same bean...
    boolean resolved = false;
    boolean autowireNecessary = false;
    if (args == null) {
      synchronized (mbd.constructorArgumentLock) {
                //一個(gè)類有多個(gè)構(gòu)造函數(shù),每個(gè)構(gòu)造函數(shù)都有不同的參數(shù),所以調(diào)用前需要先根據(jù)參數(shù)鎖定構(gòu)造函數(shù)或?qū)?yīng)的工廠方法
        if (mbd.resolvedConstructorOrFactoryMethod != null) {
          resolved = true;
          autowireNecessary = mbd.constructorArgumentsResolved;
        }
      }
    }
        //如果已經(jīng)解析過則使用解析好的構(gòu)造函數(shù)方法不需要再次鎖定
    if (resolved) {
      if (autowireNecessary) {
                //構(gòu)造函數(shù)自動(dòng)注入
        return autowireConstructor(beanName, mbd, null, null);
      }
      else {
                //使用默認(rèn)構(gòu)造函數(shù)構(gòu)造
        return instantiateBean(beanName, mbd);
      }
    }

    // Need to determine the constructor...
         // 使用構(gòu)造函數(shù)對(duì)Bean進(jìn)行實(shí)例化
    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.
        //使用默認(rèn)的構(gòu)造函數(shù)對(duì)Bean進(jìn)行實(shí)例化
    return instantiateBean(beanName, mbd);
  }

  /**
   * Instantiate the given bean using its default constructor.
   * @param beanName the name of the bean
   * @param mbd the bean definition for the bean
   * @return a BeanWrapper for the new instance
   */
    //最常見的實(shí)例化過程instantiateBean
  protected BeanWrapper instantiateBean(final String beanName, final RootBeanDefinition mbd) {
         //使用默認(rèn)的實(shí)例化策略對(duì)Bean進(jìn)行實(shí)例化,默認(rèn)的實(shí)例化策略是
    //CglibSubclassingInstantiationStrategy,也就是使用CGLIB實(shí)例化Bean 
    try {
      Object beanInstance;
      final BeanFactory parent = this;
      if (System.getSecurityManager() != null) {
        beanInstance = AccessController.doPrivileged(new PrivilegedAction<Object>() {
          @Override
          public Object run() {
            return getInstantiationStrategy().instantiate(mbd, beanName, parent);
          }
        }, getAccessControlContext());
      }
      else {
        beanInstance = getInstantiationStrategy().instantiate(mbd, beanName, parent);
      }
      BeanWrapper bw = new BeanWrapperImpl(beanInstance);
      initBeanWrapper(bw);
      return bw;
    }
    catch (Throwable ex) {
      throw new BeanCreationException(
          mbd.getResourceDescription(), beanName, "Instantiation of bean failed", ex);
    }
  }

這里使用了CGLIB對(duì)Bean進(jìn)行實(shí)例化.CGLIB是一個(gè)字節(jié)碼生成器的類庫(kù),它提供了一系列的API來提供生成和轉(zhuǎn)換Java的字節(jié)碼的功能.

在Spring AOP中也使用CGLIB對(duì)Java的字節(jié)碼進(jìn)行增強(qiáng).在IoC容器中,要了解怎樣使用CGLIB來生成Bean對(duì)象,需要看一下SimpleInstantiationStrategy類.它是Spring用來生成Bean對(duì)象的默認(rèn)類,它提供了兩種實(shí)例化Bean對(duì)象的方法

  1. 通過BeanUtils,使用了Java的反射功能
  2. 通過CGLIB來生成
public class SimpleInstantiationStrategy implements InstantiationStrategy {
@Override
  public Object instantiate(RootBeanDefinition bd, String beanName, BeanFactory owner) {
    // Don't override the class with CGLIB if no overrides.
    if (bd.getMethodOverrides().isEmpty()) {
            //這里取得指定的構(gòu)造器或者生成對(duì)象的工廠方法來對(duì)Bean進(jìn)行實(shí)例化
      Constructor<?> constructorToUse;
      synchronized (bd.constructorArgumentLock) {
        constructorToUse = (Constructor<?>) bd.resolvedConstructorOrFactoryMethod;
        if (constructorToUse == null) {
          final Class<?> clazz = bd.getBeanClass();
          if (clazz.isInterface()) {
            throw new BeanInstantiationException(clazz, "Specified class is an interface");
          }
          try {
            if (System.getSecurityManager() != null) {
              constructorToUse = AccessController.doPrivileged(new PrivilegedExceptionAction<Constructor<?>>() {
                @Override
                public Constructor<?> run() throws Exception {
                  return clazz.getDeclaredConstructor((Class[]) null);
                }
              });
            }
            else {
              constructorToUse = clazz.getDeclaredConstructor((Class[]) null);
            }
            bd.resolvedConstructorOrFactoryMethod = constructorToUse;
          }
          catch (Throwable ex) {
            throw new BeanInstantiationException(clazz, "No default constructor found", ex);
          }
        }
      }
      //通過BeanUtils進(jìn)行實(shí)例化,這個(gè)BeanUtils的實(shí)例化通過Constructor來實(shí)例化Bean,在BeanUtils中可以看到具體的調(diào)用ctor.newInstance(args)
      return BeanUtils.instantiateClass(constructorToUse);
    }
    else {   
      // 使用CGLIB來實(shí)例化對(duì)象
      return instantiateWithMethodInjection(bd, beanName, owner);
    }
  }
}

Bean之間依賴關(guān)系的處理

依賴關(guān)系處理的入口是前面提到的populateBean方法.由于其中涉及的面太多,在這里就不貼代碼了.簡(jiǎn)要介紹一下依賴關(guān)系處理的流程:在populateBean方法中,

首先取得在BeanDefinition中設(shè)置的property值,然后開始依賴注入的過程。

首先處理autowire的注入,可以byName或者是byType,之后對(duì)屬性進(jìn)行注入。

接著需要對(duì)Bean Reference進(jìn)行解析,在對(duì)ManageList、ManageSet、ManageMap等進(jìn)行解析完之后,就已經(jīng)為依賴注入準(zhǔn)備好了條件,這是真正把Bean對(duì)象設(shè)置到它所依賴的另一個(gè)Bean屬性中去的地方,其中處理的屬性是各種各樣的。

依賴注入發(fā)生在BeanWrapper的setPropertyValues中,具體的完成卻是在BeanWrapper的子類BeanWrapperImpl中實(shí)現(xiàn)的,它會(huì)完成Bean的屬性值的注入,其中包括對(duì)Array的注入、對(duì)List等集合類以及對(duì)非集合類的域進(jìn)行注入。

進(jìn)過一系列的注入,這樣就完成了對(duì)各種Bean屬性的依賴注入過程。

在Bean的創(chuàng)建和對(duì)象依賴注入的過程中,需要依據(jù)BeanDefinition中的信息來遞歸地完成依賴注入。

從前面的幾個(gè)遞歸過程中可以看到,這些遞歸都是以getBean為入口的。

一個(gè)遞歸是在上下文體系中查找需要的Bean和創(chuàng)建Bean的遞歸調(diào)用;

另一個(gè)遞歸是在依賴注入時(shí),通過遞歸調(diào)用容器的getBean方法,得到當(dāng)前Bean的依賴Bean,同時(shí)也觸發(fā)對(duì)依賴Bean的創(chuàng)建和注入。

在對(duì)Bean的屬性進(jìn)行依賴注入時(shí),解析的過程也是一個(gè)遞歸的過程。這樣,根據(jù)依賴關(guān)系,一層層地完成Bean的創(chuàng)建和注入,直到最后完成當(dāng)前Bean的創(chuàng)建。有了這個(gè)頂層Bean的創(chuàng)建和對(duì)它屬性依賴注入的完成,意味著和當(dāng)前Bean相關(guān)的整個(gè)依賴鏈的注入液完成了。

在Bean創(chuàng)建和依賴注入完成以后,在IoC容器中建立起一系列依靠依賴關(guān)系聯(lián)系起來的Bean,這個(gè)Bean已經(jīng)不再是簡(jiǎn)單的Java對(duì)象了。該Bean系列以及Bean之間的依賴關(guān)系建立完成之后,通過IoC的相關(guān)接口方法,就可以非常方便地供上層應(yīng)用使用了。

2. lazy-init屬性和預(yù)實(shí)例化

在前面的refresh方法中,我們可以看到調(diào)用了finishBeanFactoryInitialization來對(duì)配置了lazy-init的Bean進(jìn)行處理。

其實(shí)在這個(gè)方法中,封裝了對(duì)lazy-init屬性的處理,實(shí)際的處理是在DefaultListableBeanFactory這個(gè)基本容器的preInstantiateSingleton方法中完成的。該方法對(duì)單例Bean完成預(yù)實(shí)例化,這個(gè)預(yù)實(shí)例化的完成巧妙地委托給容器來實(shí)現(xiàn)。如果需要預(yù)實(shí)例化,那么就直接在這里采用getBean去觸發(fā)依賴注入,與正常依賴注入的觸發(fā)相比,只有觸發(fā)的時(shí)間和場(chǎng)合不同。在這里,依賴注入發(fā)生在容器執(zhí)行refresh的過程中,即IoC容器初始化的過程中,而不像一般的依賴注入一樣發(fā)生在IoC容器初始化完成以后,第一次通過getBean想容器索要Bean的時(shí)候。

以上就是本文的全部?jī)?nèi)容,希望對(duì)大家的學(xué)習(xí)有所幫助,也希望大家多多支持腳本之家。

相關(guān)文章

  • Spring Boot Security配置教程

    Spring Boot Security配置教程

    在本文里我們給大家分享了關(guān)于Spring Boot Security配置的相關(guān)步驟以及注意要點(diǎn),需要的朋友們跟著操作下。
    2019-05-05
  • WIN7系統(tǒng)JavaEE(tomcat7 Eclipse)環(huán)境配置教程(二)

    WIN7系統(tǒng)JavaEE(tomcat7 Eclipse)環(huán)境配置教程(二)

    這篇文章主要介紹了WIN7系統(tǒng)JavaEE(java+tomcat7+Eclipse)環(huán)境配置教程,本文重點(diǎn)在于tomcat配置、Eclipse配置,感興趣的小伙伴們可以參考一下
    2016-06-06
  • 詳解Java如何優(yōu)雅的實(shí)現(xiàn)字典翻譯

    詳解Java如何優(yōu)雅的實(shí)現(xiàn)字典翻譯

    當(dāng)我們?cè)贘ava應(yīng)用程序中需要對(duì)字典屬性進(jìn)行轉(zhuǎn)換返回給前端時(shí),如何簡(jiǎn)單、方便、并且優(yōu)雅的處理是一個(gè)重要問題。在本文中,我們將介紹如何使用Java中的序列化機(jī)制來優(yōu)雅地實(shí)現(xiàn)字典值的翻譯,從而簡(jiǎn)化開發(fā)
    2023-04-04
  • Springmvc請(qǐng)求參數(shù)類型轉(zhuǎn)換器及原生api代碼實(shí)例

    Springmvc請(qǐng)求參數(shù)類型轉(zhuǎn)換器及原生api代碼實(shí)例

    這篇文章主要介紹了Springmvc請(qǐng)求參數(shù)類型轉(zhuǎn)換器及原生api代碼實(shí)例,文中通過示例代碼介紹的非常詳細(xì),對(duì)大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價(jià)值,需要的朋友可以參考下
    2020-10-10
  • JSP 開發(fā)之 releaseSession的實(shí)例詳解

    JSP 開發(fā)之 releaseSession的實(shí)例詳解

    這篇文章主要介紹了JSP 開發(fā)之 releaseSession的實(shí)例詳解的相關(guān)資料,需要的朋友可以參考下
    2017-07-07
  • 使用opencsv文件讀寫CSV文件

    使用opencsv文件讀寫CSV文件

    這篇文章主要為大家詳細(xì)介紹了用opencsv文件讀寫CSV文件,文中示例代碼介紹的非常詳細(xì),具有一定的參考價(jià)值,感興趣的小伙伴們可以參考一下
    2019-05-05
  • Java中StringBuilder類的介紹與常用方法

    Java中StringBuilder類的介紹與常用方法

    StringBuilder是一個(gè)可變的字符串的操作類,我們可以把它看成是一個(gè)對(duì)象容器,下面這篇文章主要給大家介紹了關(guān)于Java中StringBuilder類的介紹與常用方法,文中通過示例代碼介紹的非常詳細(xì),需要的朋友可以參考下
    2022-12-12
  • SpringBoot 如何讀取classpath下的文件

    SpringBoot 如何讀取classpath下的文件

    這篇文章主要介紹了SpringBoot 讀取classpath下的文件方式,具有很好的參考價(jià)值,希望對(duì)大家有所幫助。如有錯(cuò)誤或未考慮完全的地方,望不吝賜教
    2021-06-06
  • Java特性隊(duì)列和棧的堵塞原理解析

    Java特性隊(duì)列和棧的堵塞原理解析

    這篇文章主要介紹了Java特性隊(duì)列和棧的堵塞原理解析,文中通過示例代碼介紹的非常詳細(xì),對(duì)大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價(jià)值,需要的朋友可以參考下
    2020-10-10
  • java微信開發(fā)API第四步 微信自定義個(gè)性化菜單實(shí)現(xiàn)

    java微信開發(fā)API第四步 微信自定義個(gè)性化菜單實(shí)現(xiàn)

    這篇文章主要為大家詳細(xì)介紹了java微信開發(fā)API第四步,自定義菜單以及個(gè)性化菜單實(shí)現(xiàn) ,感興趣的小伙伴們可以參考一下
    2016-06-06

最新評(píng)論

磐石市| 托里县| 黎平县| 扬州市| 花莲县| 镇坪县| 中超| 南昌县| 延庆县| 宜春市| 梅河口市| 天津市| 富阳市| 灵山县| 建湖县| 五家渠市| 普兰店市| 城步| 黄陵县| 三台县| 盱眙县| 治县。| 呼和浩特市| 宜兴市| 堆龙德庆县| 工布江达县| 横山县| 蓝山县| 孟村| 双江| 荔波县| 申扎县| 长春市| 台北县| 泰来县| 永丰县| 嘉兴市| 广德县| 启东市| 西乡县| 泰宁县|