ConfigurableListableBeanFactory 提供bean definition的解析,注冊功能,再對單例來個預加載(解決循環依賴問題).

貌似我們一般開發就會直接定義這么個接口了事.而不是像Spring這樣先根據使用情況細分那么多,到這邊再合并
ConfigurableListableBeanFactory具體：

1、2個忽略自動裝配的的方法。

2、1個注冊一個可分解依賴的方法。

3、1個判斷指定的Bean是否有資格作為自動裝配的候選者的方法。

4、1個根據指定bean名，返回注冊的Bean定義的方法。

5、2個凍結所有的Bean配置相關的方法。

6、1個使所有的非延遲加載的單例類都實例化的方法。

總結：工廠接口ConfigurableListableBeanFactory同時繼承了3個接口，ListableBeanFactory、AutowireCapableBeanFactory 和 ConfigurableBeanFactory，擴展之后，加上自有的這8個方法，這個工廠接口總共有83個方法，實在是巨大到不行了。這個工廠接口的自有方法總體上只是對父類接口功能的補充，包含了BeanFactory體系目前的所有方法，可以說是接口的集大成者。

/*** Configuration interface to be implemented by most listable bean factories.* In addition to {@link ConfigurableBeanFactory}, it provides facilities to* analyze and modify bean definitions, and to pre-instantiate singletons.** <p>This subinterface of {@link org.springframework.beans.factory.BeanFactory}* is not meant to be used in normal application code: Stick to* {@link org.springframework.beans.factory.BeanFactory} or* {@link org.springframework.beans.factory.ListableBeanFactory} for typical* use cases. This interface is just meant to allow for framework-internal* plug'n'play even when needing access to bean factory configuration methods.** @author Juergen Hoeller* @since 03.11.2003* @see org.springframework.context.support.AbstractApplicationContext#getBeanFactory()*/ public interface ConfigurableListableBeanFactoryextends ListableBeanFactory, AutowireCapableBeanFactory, ConfigurableBeanFactory {//-------------------------------------------------------------------------// 設置忽略的依賴關系,注冊找到的特殊依賴//-------------------------------------------------------------------------/*** Ignore the given dependency type for autowiring:* for example, String. Default is none.* @param type the dependency type to ignore*///忽略自動裝配的依賴類型void ignoreDependencyType(Class<?> type);/*** Ignore the given dependency interface for autowiring.* <p>This will typically be used by application contexts to register* dependencies that are resolved in other ways, like BeanFactory through* BeanFactoryAware or ApplicationContext through ApplicationContextAware.* <p>By default, only the BeanFactoryAware interface is ignored.* For further types to ignore, invoke this method for each type.* @param ifc the dependency interface to ignore* @see org.springframework.beans.factory.BeanFactoryAware* @see org.springframework.context.ApplicationContextAware*///忽略自動裝配的接口void ignoreDependencyInterface(Class<?> ifc);/*** Register a special dependency type with corresponding autowired value.* <p>This is intended for factory/context references that are supposed* to be autowirable but are not defined as beans in the factory:* e.g. a dependency of type ApplicationContext resolved to the* ApplicationContext instance that the bean is living in.* <p>Note: There are no such default types registered in a plain BeanFactory,* not even for the BeanFactory interface itself.* @param dependencyType the dependency type to register. This will typically* be a base interface such as BeanFactory, with extensions of it resolved* as well if declared as an autowiring dependency (e.g. ListableBeanFactory),* as long as the given value actually implements the extended interface.* @param autowiredValue the corresponding autowired value. This may also be an* implementation of the {@link org.springframework.beans.factory.ObjectFactory}* interface, which allows for lazy resolution of the actual target value.*//** 注冊一個可分解的依賴*/void registerResolvableDependency(Class<?> dependencyType, Object autowiredValue);/*** Determine whether the specified bean qualifies as an autowire candidate,* to be injected into other beans which declare a dependency of matching type.* <p>This method checks ancestor factories as well.* @param beanName the name of the bean to check* @param descriptor the descriptor of the dependency to resolve* @return whether the bean should be considered as autowire candidate* @throws NoSuchBeanDefinitionException if there is no bean with the given name*//** 判斷指定的Bean是否有資格作為自動裝配的候選者*/boolean isAutowireCandidate(String beanName, DependencyDescriptor descriptor)throws NoSuchBeanDefinitionException;//-------------------------------------------------------------------------// 獲取bean定義 (可以訪問屬性值跟構造方法的參數值)//-------------------------------------------------------------------------/*** Return the registered BeanDefinition for the specified bean, allowing access* to its property values and constructor argument value (which can be* modified during bean factory post-processing).* <p>A returned BeanDefinition object should not be a copy but the original* definition object as registered in the factory. This means that it should* be castable to a more specific implementation type, if necessary.* <p><b>NOTE:</b> This method does <i>not</i> consider ancestor factories.* It is only meant for accessing local bean definitions of this factory.* @param beanName the name of the bean* @return the registered BeanDefinition* @throws NoSuchBeanDefinitionException if there is no bean with the given name* defined in this factory*//** 返回注冊的Bean定義*/BeanDefinition getBeanDefinition(String beanName) throws NoSuchBeanDefinitionException;/*** Return a unified view over all bean names managed by this factory.* <p>Includes bean definition names as well as names of manually registered* singleton instances, with bean definition names consistently coming first,* analogous to how type/annotation specific retrieval of bean names works.* @return the composite iterator for the bean names view* @since 4.1.2* @see #containsBeanDefinition* @see #registerSingleton* @see #getBeanNamesForType* @see #getBeanNamesForAnnotation*/Iterator<String> getBeanNamesIterator();/*** Clear the merged bean definition cache, removing entries for beans* which are not considered eligible for full metadata caching yet.* <p>Typically triggered after changes to the original bean definitions,* e.g. after applying a {@link BeanFactoryPostProcessor}. Note that metadata* for beans which have already been created at this point will be kept around.* @since 4.2* @see #getBeanDefinition* @see #getMergedBeanDefinition*/void clearMetadataCache();//-------------------------------------------------------------------------// 鎖定配置信息.在調用refresh時會使用到.//-------------------------------------------------------------------------/*** Freeze all bean definitions, signalling that the registered bean definitions* will not be modified or post-processed any further.* <p>This allows the factory to aggressively cache bean definition metadata.*///暫時凍結所有的Bean配置void freezeConfiguration();/*** Return whether this factory's bean definitions are frozen,* i.e. are not supposed to be modified or post-processed any further.* @return {@code true} if the factory's configuration is considered frozen*///判斷本工廠配置是否被凍結boolean isConfigurationFrozen();//-------------------------------------------------------------------------// 預加載不是懶加載的單例.用于解決循環依賴問題//-------------------------------------------------------------------------/*** Ensure that all non-lazy-init singletons are instantiated, also considering* {@link org.springframework.beans.factory.FactoryBean FactoryBeans}.* Typically invoked at the end of factory setup, if desired.* @throws BeansException if one of the singleton beans could not be created.* Note: This may have left the factory with some beans already initialized!* Call {@link #destroySingletons()} for full cleanup in this case.* @see #destroySingletons()*///使所有的非延遲加載的單例類都實例化。void preInstantiateSingletons() throws BeansException;}

總結

以上是生活随笔為你收集整理的ConfigurableListableBeanFactory的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。