Spring源码——Bean如何注册到Spring IOC容器中

在Spring中对象注册到容器主要有两种方法:

  1. 使用xml配置文件对类进行配置后自动创建对象
  2. 使用注解的方式进行Bean注册

接下来将分别展示两种方式的注册过程

1 xml配置文件进行注册

总的来说,这种方法的步骤为:

  1. 保存xml配置文件的路径
  2. 根据位置读到配置文件,解析成DOM对象
  3. DOM结构的对象转换+注册成BeanDefinition
  4. 将BeanDefinition存入beanDefinitionMap
  5. 需要实例化时从beanDefinitionMap中取出

A BeanDefinition describes a bean instance, which has property values, constructor argument values, and further information supplied by concrete implementations.

BeanDefinition 描述了一个bean的实例,它含有属性值,构造方法,其他方法和由实际应用提供的进一步信息。

接下来进行源码的详细解读和分析。

首先定义变量:

public class User {
    private String userName;
    private String password;
}

在xml文件进行配置:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd">
    <bean id="userBean" class="org.kxg.springDemo.User">
        <property name="userName" value="jack" />
        <property name="password" value="123456" />
    </bean>
</beans>

读取配置文件并运行:

public class XmlBeanTest {
    public static void main(String[] args){
        ClassPathXmlApplicationContext applicationContext = new ClassPathXmlApplicationContext("bean.xml");
        User user = (User) applicationContext.getBean("userBean");
        System.out.println(user.getUserName());
    }
}

可以看到,运行过程是通过ClassPathXmlApplicationContext函数从容器中读取到变量,因此分析应从该函数入手。

函数定义如下:

//一个配置文件
public ClassPathXmlApplicationContext(String configLocation) throws BeansException {
		this(new String[] {configLocation}, true, null);
	}

//多个配置文件	
public ClassPathXmlApplicationContext(String... configLocations) throws BeansException {
	this(configLocations, true, null);
}

观察ClassPathXmlApplicationContext的构造函数,如下所示:

public ClassPathXmlApplicationContext(
			String[] configLocations, 
			boolean refresh,
			@Nullable ApplicationContext parent)throws BeansException {
				super(parent);
				//将传入的xml配置位置信息保存到configLocations
				setConfigLocations(configLocations);
				if (refresh) {
					refresh();
				}
	}

该函数传入——

  1. xml文件的路径(string数组)
  2. 是否refresh(布尔)
  3. parent

内部方法——

  1. 调用setConfigLocations方法将传入的xml路径设为configLocations
  2. 如果refresh==true,调用refresh()函数

refresh()函数如下:

public void refresh() throws BeansException, IllegalStateException {
		synchronized (this.startupShutdownMonitor) {
			// Prepare this context for refreshing.
			prepareRefresh();

			// !!!
			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.
				invokeBeanFactoryPostProcessors(beanFactory);

				// Register bean processors that intercept bean creation.
				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.
				finishBeanFactoryInitialization(beanFactory);

				// Last step: publish corresponding event.
				finishRefresh();
			}

			catch (BeansException ex) {
				if (logger.isWarnEnabled()) {
					logger.warn("Exception encountered during context initialization - " +
							"cancelling refresh attempt: " + ex);
				}

				// Destroy already created singletons to avoid dangling resources.
				destroyBeans();

				// Reset 'active' flag.
				cancelRefresh(ex);

				// Propagate exception to caller.
				throw ex;
			}

			finally {
				// Reset common introspection caches in Spring's core, since we
				// might not ever need metadata for singleton beans anymore...
				resetCommonCaches();
			}
		}
	}

其中:ConfigurableListableBeanFactory beanFactory = obtainFreshBeanFactory();
这句话调用了obtainFreshBeanFactory()函数,返回一个bean的factory(类似于工厂模式中,构建一个生产bean的工厂)。

该函数定义如下:

protected ConfigurableListableBeanFactory obtainFreshBeanFactory() {
		refreshBeanFactory();
		return getBeanFactory();
	}

可见,是通过调用refreshBeanFactory();这个方法来构建工厂的。

进而查看refreshBeanFactory()方法,如下:

protected final void refreshBeanFactory() throws BeansException {
		if (hasBeanFactory()) {
			destroyBeans();
			closeBeanFactory();
		}
		try {
		    //创建一个BeanFactory
			DefaultListableBeanFactory beanFactory = createBeanFactory();
			beanFactory.setSerializationId(getId());
			customizeBeanFactory(beanFactory);
			//这里进行Bean的加载
			loadBeanDefinitions(beanFactory);
			synchronized (this.beanFactoryMonitor) {
				this.beanFactory = beanFactory;
			}
		}
		catch (IOException ex) {
			throw new ApplicationContextException("I/O error parsing bean definition source for " + getDisplayName(), ex);
		}
	}

可见,该函数利用createBeanFactory函数创建一个beanFactory对象,接着对这个beanFactory操作,包括调用loadBeanDefinitions(beanFactory)方法来加载beanFactory。

接下来查看loadBeanDefinitions(beanFactory)方法是如何加载beanFactory的。代码如下:

protected void loadBeanDefinitions(DefaultListableBeanFactory beanFactory) throws BeansException, IOException {
		// 构造一个XmlBeanDefinitionReader,用于读到xml中配置的bean
		XmlBeanDefinitionReader beanDefinitionReader = new XmlBeanDefinitionReader(beanFactory);

		// 配置XmlBeanDefinitionReader
		beanDefinitionReader.setEnvironment(this.getEnvironment());
		beanDefinitionReader.setResourceLoader(this);
		beanDefinitionReader.setEntityResolver(new ResourceEntityResolver(this));

		//初始化XmlBeanDefinitionReader
		initBeanDefinitionReader(beanDefinitionReader);
		//加载Bean
		loadBeanDefinitions(beanDefinitionReader);
	}

可见,该函数的方式是构造一个reader(beanDefinitionReader),用于读取beanFactory的东西。先对这个reader操作(配置好环境等,再初始化一下),最后利用同名的loadBeanDefinitions(beanDefinitionReader);
加载BeanDefinitions。

这个同名的函数实现如下:

protected void loadBeanDefinitions(XmlBeanDefinitionReader reader) throws BeansException, IOException {
		Resource[] configResources = getConfigResources();
		if (configResources != null) {
			reader.loadBeanDefinitions(configResources);
		}
		String[] configLocations = getConfigLocations();
		if (configLocations != null) {
			reader.loadBeanDefinitions(configLocations);
		}
	}

这个函数将分别处理位置信息和资源信息。
getConfigResources获取配置的资源,放到名为configResourcesResource类型数组里面,判断获得的东西是不是空,如果不是,就把获得的资源传入reader.loadBeanDefinitions(configResources);

同理,还用getConfigLocations获得了配置资源的位置,用configLocations(String数组)保存,不为空时,调用reader.loadBeanDefinitions(configLocations);

至此经过一番操作,容器已经获得了配置文件的位置configLocations,接下来将根据configLocations来讲对象解析成DOM对象,最终目的是要将对象注册成BeanDefinition

观察上一步中,处理位置信息的loadBeanDefinitions,它的实现如下:

@Override
public int loadBeanDefinitions(String... locations) throws BeanDefinitionStoreException {
	Assert.notNull(locations, "Location array must not be null");
	int count = 0;
	for (String location : locations) {
		count += loadBeanDefinitions(location);
	}
	return count;
}

它传入一个configLocations(stirng数组),
对于configLocations里面的每个location,count+=loadBeanDefinitions对location的处理结果(也是int),最后返回count(int类型)

刚刚处理单个location 的函数loadBeanDefinitions,实现如下:

public int loadBeanDefinitions(String location, @Nullable Set<Resource> actualResources) throws BeanDefinitionStoreException {
		ResourceLoader resourceLoader = getResourceLoader();
		if (resourceLoader == null) {
			throw new BeanDefinitionStoreException(
					"Cannot load bean definitions from location [" + location + "]: no ResourceLoader available");
		}

		if (resourceLoader instanceof ResourcePatternResolver) {
			// Resource pattern matching available.
			try {
				Resource[] resources = ((ResourcePatternResolver) resourceLoader).getResources(location);
				int count = loadBeanDefinitions(resources);
				if (actualResources != null) {
					Collections.addAll(actualResources, resources);
				}
				if (logger.isTraceEnabled()) {
					logger.trace("Loaded " + count + " bean definitions from location pattern [" + location + "]");
				}
				return count;
			}
			catch (IOException ex) {
				throw new BeanDefinitionStoreException(
						"Could not resolve bean definition resource pattern [" + location + "]", ex);
			}
		}
		else {
			// Can only load single resources by absolute URL.
			Resource resource = resourceLoader.getResource(location);
			int count = loadBeanDefinitions(resource);
			if (actualResources != null) {
				actualResources.add(resource);
			}
			if (logger.isTraceEnabled()) {
				logger.trace("Loaded " + count + " bean definitions from location [" + location + "]");
			}
			return count;
		}
	}

这个函数首先用getResourceLoader,得到一个resourceLoader(资源加载器)。再判断resourceLoader是否为ResourcePatternResolver的一个实例(instance of),这个判断的目的是判断后面调用getResources(location)时,是传入Resource类型的数组还是变量。

如果是实例,则:
getResources(location)函数,返回一个名为resources的Resource数组,再int count = loadBeanDefinitions(resources);

否则:
getResources(location)函数,返回一个名为resource的Resource变量
int count = loadBeanDefinitions(resource);

总之都是调用loadBeanDefinitions(resource)

这个loadBeanDefinitions(resource)函数,定义如下:

public int loadBeanDefinitions(EncodedResource encodedResource) throws BeanDefinitionStoreException {
		Assert.notNull(encodedResource, "EncodedResource must not be null");
		if (logger.isTraceEnabled()) {
			logger.trace("Loading XML bean definitions from " + encodedResource);
		}

		Set<EncodedResource> currentResources = this.resourcesCurrentlyBeingLoaded.get();
		if (currentResources == null) {
			currentResources = new HashSet<>(4);
			this.resourcesCurrentlyBeingLoaded.set(currentResources);
		}
		if (!currentResources.add(encodedResource)) {
			throw new BeanDefinitionStoreException(
					"Detected cyclic loading of " + encodedResource + " - check your import definitions!");
		}
		try {
			InputStream inputStream = encodedResource.getResource().getInputStream();
			try {
				InputSource inputSource = new InputSource(inputStream);
				if (encodedResource.getEncoding() != null) {
					inputSource.setEncoding(encodedResource.getEncoding());
				}
				//进行BeanDefinations加载
				return doLoadBeanDefinitions(inputSource, encodedResource.getResource());
			}
			finally {
				inputStream.close();
			}
		}
		catch (IOException ex) {
			throw new BeanDefinitionStoreException(
					"IOException parsing XML document from " + encodedResource.getResource(), ex);
		}
		finally {
			currentResources.remove(encodedResource);
			if (currentResources.isEmpty()) {
				this.resourcesCurrentlyBeingLoaded.remove();
			}
		}
	}

把传入的resource,调用getResource函数+getInputStream函数,变成一个InputStream 类型的变量inputStream,再用InputSource方法把inputStream变成InputSource 类型的变量inputSource
最后返回:doLoadBeanDefinitions(inputSource, encodedResource. getResource())的结果。

而这个doLoadBeanDefinitions实现如下:

protected int doLoadBeanDefinitions(InputSource inputSource, Resource resource)
			throws BeanDefinitionStoreException {

		try {
		    //构造xml的Document结构,解析DOM结构
			Document doc = doLoadDocument(inputSource, resource);
			//注册BeanDefinition
			int count = registerBeanDefinitions(doc, resource);
			if (logger.isDebugEnabled()) {
				logger.debug("Loaded " + count + " bean definitions from " + resource);
			}
			return count;
		}
		catch (BeanDefinitionStoreException ex) {
			throw ex;
		}
		catch (SAXParseException ex) {
			throw new XmlBeanDefinitionStoreException(resource.getDescription(),
					"Line " + ex.getLineNumber() + " in XML document from " + resource + " is invalid", ex);
		}
		catch (SAXException ex) {
			throw new XmlBeanDefinitionStoreException(resource.getDescription(),
					"XML document from " + resource + " is invalid", ex);
		}
		catch (ParserConfigurationException ex) {
			throw new BeanDefinitionStoreException(resource.getDescription(),
					"Parser configuration exception parsing XML from " + resource, ex);
		}
		catch (IOException ex) {
			throw new BeanDefinitionStoreException(resource.getDescription(),
					"IOException parsing XML document from " + resource, ex);
		}
		catch (Throwable ex) {
			throw new BeanDefinitionStoreException(resource.getDescription(),
					"Unexpected exception parsing XML document from " + resource, ex);
		}
	}

内部调用doLoadDocument函数,传入inputSourceresource,返回Document类型的变量doc,再调用registerBeanDefinitions函数(传入doc和resource,返回一个int值)。

至此,已经将配置文件解析转换成DOM对象了,接下来要正式进行注册了(将DOM转换成BeanDefinition类型)。

刚刚被调用的registerBeanDefinitions函数,实现如下:

public int registerBeanDefinitions(Document doc, Resource resource) throws BeanDefinitionStoreException {
		BeanDefinitionDocumentReader documentReader = createBeanDefinitionDocumentReader();
		int countBefore = getRegistry().getBeanDefinitionCount();
		documentReader.registerBeanDefinitions(doc, createReaderContext(resource));
		return getRegistry().getBeanDefinitionCount() - countBefore;
	}

它构造了一个BeanDefinitionDocumentReader类型的变量,调用registerBeanDefinitions函数注册BeanDefinition,并且返回了本次注册Bean的数量。

而实现注册的方法为:doRegisterBeanDefinitions
该方法实现如下:

protected void doRegisterBeanDefinitions(Element root) {
		// Any nested <beans> elements will cause recursion in this method. In
		// order to propagate and preserve <beans> default-* attributes correctly,
		// keep track of the current (parent) delegate, which may be null. Create
		// the new (child) delegate with a reference to the parent for fallback purposes,
		// then ultimately reset this.delegate back to its original (parent) reference.
		// this behavior emulates a stack of delegates without actually necessitating one.
		BeanDefinitionParserDelegate parent = this.delegate;
		this.delegate = createDelegate(getReaderContext(), root, parent);

		if (this.delegate.isDefaultNamespace(root)) {
			String profileSpec = root.getAttribute(PROFILE_ATTRIBUTE);
			if (StringUtils.hasText(profileSpec)) {
				String[] specifiedProfiles = StringUtils.tokenizeToStringArray(
						profileSpec, BeanDefinitionParserDelegate.MULTI_VALUE_ATTRIBUTE_DELIMITERS);
				// We cannot use Profiles.of(...) since profile expressions are not supported
				// in XML config. See SPR-12458 for details.
				if (!getReaderContext().getEnvironment().acceptsProfiles(specifiedProfiles)) {
					if (logger.isDebugEnabled()) {
						logger.debug("Skipped XML bean definition file due to specified profiles [" + profileSpec +
								"] not matching: " + getReaderContext().getResource());
					}
					return;
				}
			}
		}

		preProcessXml(root);
		//进行BeanDefinition转换,将DOM结构的对象转换成BeanDefinition
		parseBeanDefinitions(root, this.delegate);
		postProcessXml(root);

		this.delegate = parent;
	}

可以看到里面的parseBeanDefinitions就是将DOM转换成BeanDefinition的函数。

这个parseBeanDefinitions的实现如下:

protected void parseBeanDefinitions(Element root, BeanDefinitionParserDelegate delegate) {
		if (delegate.isDefaultNamespace(root)) {
			NodeList nl = root.getChildNodes();
			for (int i = 0; i < nl.getLength(); i++) {
				Node node = nl.item(i);
				if (node instanceof Element) {
					Element ele = (Element) node;
					if (delegate.isDefaultNamespace(ele)) {
					    //Spring默认元素转换
						parseDefaultElement(ele, delegate);
					}
					else {
					    //xml中自定义的Element进行解析
						delegate.parseCustomElement(ele);
					}
				}
			}
		}
		else {
			delegate.parseCustomElement(root);
		}
	}

可见,它内部调用parseDefaultElement方法,对元素进行配置,如下:

private void parseDefaultElement(Element ele, BeanDefinitionParserDelegate delegate) {
		if (delegate.nodeNameEquals(ele, IMPORT_ELEMENT)) {
			importBeanDefinitionResource(ele);
		}
		else if (delegate.nodeNameEquals(ele, ALIAS_ELEMENT)) {
			processAliasRegistration(ele);
		}
		else if (delegate.nodeNameEquals(ele, BEAN_ELEMENT)) {
			processBeanDefinition(ele, delegate);
		}
		else if (delegate.nodeNameEquals(ele, NESTED_BEANS_ELEMENT)) {
			// recurse
			doRegisterBeanDefinitions(ele);
		}
	}

可以看到,它对import、alias、bean、beans这几个元素进行了分析,这几个也是xml配置文件的默认配置元素。

这里面调用的processBeanDefinition用于对bean元素加工处理,如下:

protected void processBeanDefinition(Element ele, BeanDefinitionParserDelegate delegate) {
		BeanDefinitionHolder bdHolder = delegate.parseBeanDefinitionElement(ele);
		if (bdHolder != null) {
			bdHolder = delegate.decorateBeanDefinitionIfRequired(ele, bdHolder);
			try {
				// Register the final decorated instance.
				BeanDefinitionReaderUtils.registerBeanDefinition(bdHolder, getReaderContext().getRegistry());
			}
			catch (BeanDefinitionStoreException ex) {
				getReaderContext().error("Failed to register bean definition with name '" +
						bdHolder.getBeanName() + "'", ele, ex);
			}
			// Send registration event.
			getReaderContext().fireComponentRegistered(new BeanComponentDefinition(bdHolder));
		}
	}

processXXX函数内部调用的registerBeanDefinition将会把bean正式进行注册,如下:

public static void registerBeanDefinition(
			BeanDefinitionHolder definitionHolder, BeanDefinitionRegistry registry)
			throws BeanDefinitionStoreException {

		// Register bean definition under primary name.
		String beanName = definitionHolder.getBeanName();
		//注册BeanDefinition
		registry.registerBeanDefinition(beanName, definitionHolder.getBeanDefinition());

		// Register aliases for bean name, if any.
		String[] aliases = definitionHolder.getAliases();
		if (aliases != null) {
			for (String alias : aliases) {
				registry.registerAlias(beanName, alias);
			}
		}
	}

至此,已经成功的将DOM对象注册成为BeanDefinition,接下来将BeanDefinition进行存储。

刚刚的函数内部又调用了同名的registerBeanDefinition,这个同名的函数将会把BeanDefinition存储到beanDefinitionMap中,实现如下:

// DefaultListableBeanFactory
public void registerBeanDefinition(String beanName, BeanDefinition beanDefinition)
			throws BeanDefinitionStoreException {

		Assert.hasText(beanName, "Bean name must not be empty");
		Assert.notNull(beanDefinition, "BeanDefinition must not be null");

		if (beanDefinition instanceof AbstractBeanDefinition) {
			try {
				((AbstractBeanDefinition) beanDefinition).validate();
			}
			catch (BeanDefinitionValidationException ex) {
				throw new BeanDefinitionStoreException(beanDefinition.getResourceDescription(), beanName,
						"Validation of bean definition failed", ex);
			}
		}

		BeanDefinition existingDefinition = this.beanDefinitionMap.get(beanName);
		if (existingDefinition != null) {
			if (!isAllowBeanDefinitionOverriding()) {
				throw new BeanDefinitionOverrideException(beanName, beanDefinition, existingDefinition);
			}
			else if (existingDefinition.getRole() < beanDefinition.getRole()) {
				// e.g. was ROLE_APPLICATION, now overriding with ROLE_SUPPORT or ROLE_INFRASTRUCTURE
				if (logger.isInfoEnabled()) {
					logger.info("Overriding user-defined bean definition for bean '" + beanName +
							"' with a framework-generated bean definition: replacing [" +
							existingDefinition + "] with [" + beanDefinition + "]");
				}
			}
			else if (!beanDefinition.equals(existingDefinition)) {
				if (logger.isDebugEnabled()) {
					logger.debug("Overriding bean definition for bean '" + beanName +
							"' with a different definition: replacing [" + existingDefinition +
							"] with [" + beanDefinition + "]");
				}
			}
			else {
				if (logger.isTraceEnabled()) {
					logger.trace("Overriding bean definition for bean '" + beanName +
							"' with an equivalent definition: replacing [" + existingDefinition +
							"] with [" + beanDefinition + "]");
				}
			}
			//将beanDefinition放入beanDefinitionMap中
			this.beanDefinitionMap.put(beanName, beanDefinition);
		}
		else {
			if (hasBeanCreationStarted()) {
				// Cannot modify startup-time collection elements anymore (for stable iteration)
				synchronized (this.beanDefinitionMap) {
				    //将beanDefinition放入beanDefinitionMap中
					this.beanDefinitionMap.put(beanName, beanDefinition);
					List<String> updatedDefinitions = new ArrayList<>(this.beanDefinitionNames.size() + 1);
					updatedDefinitions.addAll(this.beanDefinitionNames);
					updatedDefinitions.add(beanName);
					this.beanDefinitionNames = updatedDefinitions;
					removeManualSingletonName(beanName);
				}
			}
			else {
				// Still in startup registration phase
				//将beanDefinition放入beanDefinitionMap中
				this.beanDefinitionMap.put(beanName, beanDefinition);
				this.beanDefinitionNames.add(beanName);
				removeManualSingletonName(beanName);
			}
			this.frozenBeanDefinitionNames = null;
		}

		if (existingDefinition != null || containsSingleton(beanName)) {
			resetBeanDefinition(beanName);
		}
	}

该函数把注册的BeanDefinition存到一个键为beanName,值为beanDefinition对象的Map集合中。

这个Map的定义为:

private final Map<String, BeanDefinition> beanDefinitionMap = new ConcurrentHashMap<>(256);

至此,正式完成xml配置文件方式的注册。

完成存储以后,即真正注册到容器中了。当需要使用的时候,再进行实例化从容器(Map)中取出。

2 注解方式下Bean的注册

总的来说,该方法的主要步骤为:

  1. 根据包名,扫描包下面带注解的类
  2. 将带注解的都用registerBeanDefinition进行注册,转换成BeanDefinition
  3. BeanDefinition都存储到set中

同样的,先创建对象,如下:

@Component
public class AnnotionConfig {
    @Bean(name = "userBean")
    public User getUserBean(){
        User user = new User();
        user.setUserName("Lucy");
        return user;
    }
}

测试容器是否拿到对象:

public class AnnotionBeanTest {
    public static void main(String[] args){
        AnnotationConfigApplicationContext applicationContext = new AnnotationConfigApplicationContext("org.kxg.springDemo");
        User user = (User) applicationContext.getBean("userBean");
        System.out.println(user.getUserName());
    }
}

这里调用的是AnnotationConfigApplicationContext的构造函数,传入包名,自动扫描包下面的Spring注解,然后将其注册到容器中。

它的构造方法具体如下:

public AnnotationConfigApplicationContext(String... basePackages) {
		this();
		//主要是scan方法完成bean的注册
		scan(basePackages);
		//同样的调用了refresh方法
		refresh();
	}

可见,该函数内部调用scan函数,根据传入的包名,扫描包名对应的包的内容,如下:

public int scan(String... basePackages) {
		int beanCountAtScanStart = this.registry.getBeanDefinitionCount();
        //扫描包,进行Bean注册
		doScan(basePackages);

		// Register annotation config processors, if necessary.
		if (this.includeAnnotationConfig) {
			AnnotationConfigUtils.registerAnnotationConfigProcessors(this.registry);
		}

		return (this.registry.getBeanDefinitionCount() - beanCountAtScanStart);
	}

而这个scan函数又调用doScan(basePackages)函数。实现如下:

//ClassPathBeanDefinitionScanner
protected Set<BeanDefinitionHolder> doScan(String... basePackages) {
		Assert.notEmpty(basePackages, "At least one base package must be specified");
		Set<BeanDefinitionHolder> beanDefinitions = new LinkedHashSet<>();
		for (String basePackage : basePackages) {
		    //扫描包下打了注解的类,并将其转换成BeanDefinition
			Set<BeanDefinition> candidates = findCandidateComponents(basePackage);
			for (BeanDefinition candidate : candidates) {
				ScopeMetadata scopeMetadata = this.scopeMetadataResolver.resolveScopeMetadata(candidate);
				candidate.setScope(scopeMetadata.getScopeName());
				String beanName = this.beanNameGenerator.generateBeanName(candidate, this.registry);
				if (candidate instanceof AbstractBeanDefinition) {
					postProcessBeanDefinition((AbstractBeanDefinition) candidate, beanName);
				}
				if (candidate instanceof AnnotatedBeanDefinition) {
					AnnotationConfigUtils.processCommonDefinitionAnnotations((AnnotatedBeanDefinition) candidate);
				}
				if (checkCandidate(beanName, candidate)) {
					BeanDefinitionHolder definitionHolder = new BeanDefinitionHolder(candidate, beanName);
					definitionHolder =
							AnnotationConfigUtils.applyScopedProxyMode(scopeMetadata, definitionHolder, this.registry);
					beanDefinitions.add(definitionHolder);
					//进行BeanDefinition注册
					registerBeanDefinition(definitionHolder, this.registry);
				}
			}
		}
		return beanDefinitions;
	}

可见,doScan函数会扫描包下打了注解的类,进行BeanDefinition注册(和上一个一样,也是调用registerBeanDefinition函数),并将其转换成BeanDefinition,最后返回一个名为beanDefinitions的集合Set<BeanDefinitionHolder>

其中调用的registerBeanDefinition函数,会根据bean的name,alias等把它注册成为一个正式的有定义的bean变量。如下:

public static void registerBeanDefinition(
			BeanDefinitionHolder definitionHolder, BeanDefinitionRegistry registry)
			throws BeanDefinitionStoreException {

		// Register bean definition under primary name.
		String beanName = definitionHolder.getBeanName();
		registry.registerBeanDefinition(beanName, definitionHolder.getBeanDefinition());

		// Register aliases for bean name, if any.
		String[] aliases = definitionHolder.getAliases();
		if (aliases != null) {
			for (String alias : aliases) {
				registry.registerAlias(beanName, alias);
			}
		}
	}

至此,完成了注解方式下的bean注册。

  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值