SpringApplication之createApplicationContext

//这里实例化的是SERVLET,即AnnotationConfigServletWebServerApplicationContext
context = createApplicationContext();
	public static final String DEFAULT_SERVLET_WEB_CONTEXT_CLASS = "org.springframework.boot."
			+ "web.servlet.context.AnnotationConfigServletWebServerApplicationContext";
	protected ConfigurableApplicationContext createApplicationContext() {
		Class<?> contextClass = this.applicationContextClass;
		if (contextClass == null) {
			try {
				switch (this.webApplicationType) {
				case SERVLET:
					contextClass = Class.forName(DEFAULT_SERVLET_WEB_CONTEXT_CLASS);
					break;
				case REACTIVE:
					contextClass = Class.forName(DEFAULT_REACTIVE_WEB_CONTEXT_CLASS);
					break;
				default:
					contextClass = Class.forName(DEFAULT_CONTEXT_CLASS);
				}
			}
			catch (ClassNotFoundException ex) {
				throw new IllegalStateException(
						"Unable create a default ApplicationContext, " + "please specify an ApplicationContextClass",
						ex);
			}
		}
		return (ConfigurableApplicationContext) BeanUtils.instantiateClass(contextClass);
	}
//调用的是无参数构造器,这里跟进去看这两个默认参数实例化做了什么
	public AnnotationConfigServletWebServerApplicationContext() {
		this.reader = new AnnotatedBeanDefinitionReader(this);
		this.scanner = new ClassPathBeanDefinitionScanner(this);
	}
//AnnotatedBeanDefinitionReader
	public AnnotatedBeanDefinitionReader(BeanDefinitionRegistry registry) {
		this(registry, getOrCreateEnvironment(registry));
	}
	public AnnotatedBeanDefinitionReader(BeanDefinitionRegistry registry, Environment environment) {
		Assert.notNull(registry, "BeanDefinitionRegistry must not be null");
		Assert.notNull(environment, "Environment must not be null");
		this.registry = registry;
		this.conditionEvaluator = new ConditionEvaluator(registry, environment, null);
		AnnotationConfigUtils.registerAnnotationConfigProcessors(this.registry);
	}
	public static void registerAnnotationConfigProcessors(BeanDefinitionRegistry registry) {
		registerAnnotationConfigProcessors(registry, null);
	}
//这里很重要,向context中注册了一些必要的beandef
//CONFIGURATION_ANNOTATION_PROCESSOR_BEAN_NAME,"org.springframework.context.annotation.internalConfigurationAnnotationProcessor"
//ConfigurationClassPostProcessor.class
//AUTOWIRED_ANNOTATION_PROCESSOR_BEAN_NAME,org.springframework.context.annotation.internalAutowiredAnnotationProcessor
//AutowiredAnnotationBeanPostProcessor.class
//COMMON_ANNOTATION_PROCESSOR_BEAN_NAME,org.springframework.context.annotation.internalCommonAnnotationProcessor
//CommonAnnotationBeanPostProcessor.class
//EVENT_LISTENER_PROCESSOR_BEAN_NAME,org.springframework.context.event.internalEventListenerProcessor
//EventListenerMethodProcessor.class
//EVENT_LISTENER_FACTORY_BEAN_NAME,org.springframework.context.event.internalEventListenerFactory
//DefaultEventListenerFactory.class
	public static Set<BeanDefinitionHolder> registerAnnotationConfigProcessors(
			BeanDefinitionRegistry registry, @Nullable Object source) {

		DefaultListableBeanFactory beanFactory = unwrapDefaultListableBeanFactory(registry);
		if (beanFactory != null) {
			if (!(beanFactory.getDependencyComparator() instanceof AnnotationAwareOrderComparator)) {
				beanFactory.setDependencyComparator(AnnotationAwareOrderComparator.INSTANCE);
			}
			if (!(beanFactory.getAutowireCandidateResolver() instanceof ContextAnnotationAutowireCandidateResolver)) {
				beanFactory.setAutowireCandidateResolver(new ContextAnnotationAutowireCandidateResolver());
			}
		}

		Set<BeanDefinitionHolder> beanDefs = new LinkedHashSet<>(8);

		if (!registry.containsBeanDefinition(CONFIGURATION_ANNOTATION_PROCESSOR_BEAN_NAME)) {
			RootBeanDefinition def = new RootBeanDefinition(ConfigurationClassPostProcessor.class);
			def.setSource(source);
			beanDefs.add(registerPostProcessor(registry, def, CONFIGURATION_ANNOTATION_PROCESSOR_BEAN_NAME));
		}

		if (!registry.containsBeanDefinition(AUTOWIRED_ANNOTATION_PROCESSOR_BEAN_NAME)) {
			RootBeanDefinition def = new RootBeanDefinition(AutowiredAnnotationBeanPostProcessor.class);
			def.setSource(source);
			beanDefs.add(registerPostProcessor(registry, def, AUTOWIRED_ANNOTATION_PROCESSOR_BEAN_NAME));
		}

		// Check for JSR-250 support, and if present add the CommonAnnotationBeanPostProcessor.
		if (jsr250Present && !registry.containsBeanDefinition(COMMON_ANNOTATION_PROCESSOR_BEAN_NAME)) {
			RootBeanDefinition def = new RootBeanDefinition(CommonAnnotationBeanPostProcessor.class);
			def.setSource(source);
			beanDefs.add(registerPostProcessor(registry, def, COMMON_ANNOTATION_PROCESSOR_BEAN_NAME));
		}

		// Check for JPA support, and if present add the PersistenceAnnotationBeanPostProcessor.
		if (jpaPresent && !registry.containsBeanDefinition(PERSISTENCE_ANNOTATION_PROCESSOR_BEAN_NAME)) {
			RootBeanDefinition def = new RootBeanDefinition();
			try {
				def.setBeanClass(ClassUtils.forName(PERSISTENCE_ANNOTATION_PROCESSOR_CLASS_NAME,
						AnnotationConfigUtils.class.getClassLoader()));
			}
			catch (ClassNotFoundException ex) {
				throw new IllegalStateException(
						"Cannot load optional framework class: " + PERSISTENCE_ANNOTATION_PROCESSOR_CLASS_NAME, ex);
			}
			def.setSource(source);
			beanDefs.add(registerPostProcessor(registry, def, PERSISTENCE_ANNOTATION_PROCESSOR_BEAN_NAME));
		}

		if (!registry.containsBeanDefinition(EVENT_LISTENER_PROCESSOR_BEAN_NAME)) {
			RootBeanDefinition def = new RootBeanDefinition(EventListenerMethodProcessor.class);
			def.setSource(source);
			beanDefs.add(registerPostProcessor(registry, def, EVENT_LISTENER_PROCESSOR_BEAN_NAME));
		}

		if (!registry.containsBeanDefinition(EVENT_LISTENER_FACTORY_BEAN_NAME)) {
			RootBeanDefinition def = new RootBeanDefinition(DefaultEventListenerFactory.class);
			def.setSource(source);
			beanDefs.add(registerPostProcessor(registry, def, EVENT_LISTENER_FACTORY_BEAN_NAME));
		}

		return beanDefs;
	}
//这里在看ClassPathBeanDefinitionScanner
	public ClassPathBeanDefinitionScanner(BeanDefinitionRegistry registry) {
		this(registry, true);
	}
	public ClassPathBeanDefinitionScanner(BeanDefinitionRegistry registry, boolean useDefaultFilters) {
		this(registry, useDefaultFilters, getOrCreateEnvironment(registry));
	}
	public ClassPathBeanDefinitionScanner(BeanDefinitionRegistry registry, boolean useDefaultFilters,
			Environment environment) {

		this(registry, useDefaultFilters, environment,
				(registry instanceof ResourceLoader ? (ResourceLoader) registry : null));
	}
	public ClassPathBeanDefinitionScanner(BeanDefinitionRegistry registry, boolean useDefaultFilters,
			Environment environment, @Nullable ResourceLoader resourceLoader) {

		Assert.notNull(registry, "BeanDefinitionRegistry must not be null");
		this.registry = registry;

		if (useDefaultFilters) {//true
			registerDefaultFilters();
		}
		setEnvironment(environment);
		setResourceLoader(resourceLoader);
	}
	//拦截被Component以及子注解标注的类
	protected void registerDefaultFilters() {
		this.includeFilters.add(new AnnotationTypeFilter(Component.class));
		ClassLoader cl = ClassPathScanningCandidateComponentProvider.class.getClassLoader();
		try {
			this.includeFilters.add(new AnnotationTypeFilter(
					((Class<? extends Annotation>) ClassUtils.forName("javax.annotation.ManagedBean", cl)), false));
			logger.trace("JSR-250 'javax.annotation.ManagedBean' found and supported for component scanning");
		}
		catch (ClassNotFoundException ex) {
			// JSR-250 1.1 API (as included in Java EE 6) not available - simply skip.
		}
		try {
			this.includeFilters.add(new AnnotationTypeFilter(
					((Class<? extends Annotation>) ClassUtils.forName("javax.inject.Named", cl)), false));
			logger.trace("JSR-330 'javax.inject.Named' annotation found and supported for component scanning");
		}
		catch (ClassNotFoundException ex) {
			// JSR-330 API not available - simply skip.
		}
	}

//这里在看AnnotationConfigServletWebServerApplicationContext父类构造器
public class AnnotationConfigServletWebServerApplicationContext extends ServletWebServerApplicationContext
		implements AnnotationConfigRegistry
//什么都没做 
	public ServletWebServerApplicationContext() {
	}
//在看父类
public class ServletWebServerApplicationContext extends GenericWebApplicationContext
		implements ConfigurableWebServerApplicationContext 
	public GenericWebApplicationContext() {
		super();
	}
//继续父类
public class GenericWebApplicationContext extends GenericApplicationContext
		implements ConfigurableWebApplicationContext, ThemeSource 
//这里初始化了DefaultListableBeanFactory,后文解析
	public GenericApplicationContext() {
		this.beanFactory = new DefaultListableBeanFactory();
	}
//在看父类
public class GenericApplicationContext extends AbstractApplicationContext implements BeanDefinitionRegistry 
	public AbstractApplicationContext() {
		this.resourcePatternResolver = getResourcePatternResolver();
	}
//初始化了 PathMatchingResourcePatternResolver
	protected ResourcePatternResolver getResourcePatternResolver() {
		return new PathMatchingResourcePatternResolver(this);
	}
//继续,这里获取默认classloader
public abstract class AbstractApplicationContext extends DefaultResourceLoader
		implements ConfigurableApplicationContext
	public DefaultResourceLoader() {
		this.classLoader = ClassUtils.getDefaultClassLoader();
	}

### 回答1: SpringApplicationSpring Boot框架中的一个核心类,它提供了一种快速创建Spring应用程序的方式。近年来,随着Spring Boot的流行,SpringApplication也因其简单易用、高效快速的特点而备受欢迎,因此被称为“爆红”。 ### 回答2: SpringApplicationSpring框架中的一个核心类,它主要用于简化Spring应用程序的启动和配置过程。最近,SpringApplication变得越来越受欢迎,这可能归功于以下几个原因。 首先,SpringApplication提供了一种快速、方便的方式来启动Spring应用程序。传统的Spring启动方法需要编写一些繁琐的配置代码,而使用SpringApplication可以通过少量的代码实现应用程序的初始化和启动。这让开发者能够更专注于业务逻辑的实现,而不必花太多时间和精力在繁杂的配置上。 其次,SpringApplication提供了自动配置功能。它能够根据应用程序的依赖和环境,自动为应用程序提供一些默认的配置。这样一来,开发者不需要手动去配置很多繁琐的东西,而是可以直接使用默认配置来启动应用程序。这大大提高了开发效率,并且减少了出错的可能性。 此外,SpringApplication还提供了丰富的扩展点和事件机制。开发者可以通过扩展SpringApplication类或者实现相应的接口,来满足自己的特定需求。同时,SpringApplication还支持事件机制,当应用程序达到某个特定的状态时,可以触发一些自定义的事件处理逻辑。 总之,SpringApplication在简化Spring应用程序启动和配置的过程方面表现出色,它的普及可能归因于它的简洁、便捷和灵活性。无论是新手还是有经验的开发者,在开发Spring应用程序时,都可以受益于这个强大的工具。 ### 回答3: SpringApplication的爆红可以从以下几个方面解释: 首先,SpringApplicationSpring Boot框架中的核心类之一,用于引导和启动一个Spring应用程序。在过去几年中,Spring Boot的使用率呈现出爆发式的增长,这也导致SpringApplication变得越来越受欢迎。 其次,SpringApplication提供了一种简化和标准化的方式来配置和启动Spring应用程序。它自动处理了大量繁琐的配置工作,如ApplicationContext的创建、自动装配Spring Bean、加载配置文件等等。这不仅减少了开发人员的工作量,还提高了开发效率,因此备受广大开发者的喜爱和追捧。 此外,SpringApplication还提供了一系列的扩展功能和便利性方法,使得开发者可以更加灵活地定制和配置Spring应用程序。例如,可以通过SpringApplication.setDefaultProperties()方法设置默认的应用程序属性,也可以通过SpringApplication.addListeners()方法添加自定义的监听器等等。这些功能和方法使得SpringApplication成为开发者们的首选,促使其爆红。 最后,SpringApplication还与Spring Boot的微服务架构密切相关。近年来,微服务架构在企业应用开发中越来越受到重视,Spring Boot作为一种用于构建和部署微服务的开发框架,其应用程序启动类SpringApplication的重要性也随之提升。众多企业和开发团队使用Spring Boot和SpringApplication来开发和部署自己的微服务,推动了SpringApplication的爆红。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值