网站建设核心点,tp框架做餐饮网站,软件开发培训费用,软文营销为什么要讲故事ConfigurableListableBeanFactory 提供bean definition的解析,注册功能,再对单例来个预加载(解决循环依赖问题). 貌似我们一般开发就会直接定义这么个接口了事.而不是像Spring这样先根据使用情况细分那么多,到这边再合并 ConfigurableListableBeanFactory具体#xff1a; 1、…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.** pThis 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* plugnplay 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.* pThis will typically be used by application contexts to register* dependencies that are resolved in other ways, like BeanFactory through* BeanFactoryAware or ApplicationContext through ApplicationContextAware.* pBy 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.* pThis 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.* pNote: 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.* pThis 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).* pA 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.* pbNOTE:/b This method does inot/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.* pIncludes 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*/IteratorString getBeanNamesIterator();/*** Clear the merged bean definition cache, removing entries for beans* which are not considered eligible for full metadata caching yet.* pTypically 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.* pThis allows the factory to aggressively cache bean definition metadata.*///暂时冻结所有的Bean配置void freezeConfiguration();/*** Return whether this factorys bean definitions are frozen,* i.e. are not supposed to be modified or post-processed any further.* return {code true} if the factorys 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;}