SpringBoot 刷新上下文1--主流程

SpringBoot刷新上下文一共七篇,基于SpringBoot 2.2.7.RELEASE,Spring 5.2.6.RELEASE
SpringBoot 刷新上下文1–主流程
SpringBoot 刷新上下文2–执行BeanDefinitionRegistryPostProcessor
SpringBoot 刷新上下文3–解析引导类
SpringBoot 刷新上下文4–处理ComponentScan
SpringBoot 刷新上下文5–处理其他注解
SpringBoot 刷新上下文6–加载并注册BeanDefinition
SpringBoot 刷新上下文7–执行BeanFactoryPostProcessor

SpringBoot刷新上下文,在run方法里面调refreshContext 方法。

//org.springframework.boot.SpringApplication#refreshContext
private void refreshContext(ConfigurableApplicationContext context) {
	refresh(context);
	if (this.registerShutdownHook) {
		try {
			context.registerShutdownHook();
		}
		catch (AccessControlException ex) {
			// Not allowed in some environments.
		}
	}
}

调了本类的refresh

//org.springframework.boot.SpringApplication#refresh
protected void refresh(ApplicationContext applicationContext) {
    Assert.isInstanceOf(AbstractApplicationContext.class, applicationContext);
    //执行上下文的刷新方法
    ((AbstractApplicationContext) applicationContext).refresh();
}

AbstractApplicationContext 的 refresh 方法。从这里就进入了Spring的上下文。

public void refresh() throws BeansException, IllegalStateException {
    synchronized (this.startupShutdownMonitor) {
		...

        // Tell the subclass to refresh the internal bean factory.
        ConfigurableListableBeanFactory beanFactory = obtainFreshBeanFactory();

		...

            // Invoke factory processors registered as beans in the context.
            invokeBeanFactoryPostProcessors(beanFactory);

            ...
    }
}

这里只看 AbstractApplicationContext#refresh 中的两个方法,obtainFreshBeanFactory 用来获得BeanFactory,invokeBeanFactoryPostProcessors 用来初始化Spring的IOC。

1、获得BeanFactory

//org.springframework.context.support.AbstractApplicationContext#obtainFreshBeanFactory
protected ConfigurableListableBeanFactory obtainFreshBeanFactory() {
    refreshBeanFactory();
    return getBeanFactory();
}

SpringBoot会根据环境创建三种上下文:

AnnotationConfigServletWebServerApplicationContext

AnnotationConfigReactiveWebServerApplicationContext

AnnotationConfigApplicationContext。

这三种上下文都继承了 GenericApplicationContext ,GenericApplicationContext 继承了 AbstractApplicationContext 。

1.1、刷新BeanFactory

private final AtomicBoolean refreshed = new AtomicBoolean();
private final DefaultListableBeanFactory beanFactory;
//org.springframework.context.support.GenericApplicationContext#refreshBeanFactory
protected final void refreshBeanFactory() throws IllegalStateException {
    if (!this.refreshed.compareAndSet(false, true)) {
        throw new IllegalStateException(
            "GenericApplicationContext does not support multiple refresh attempts: just call 'refresh' once");
    }
    this.beanFactory.setSerializationId(getId());
}

这个方法并没有做什么处理,不像 ClassPathXmlApplicationContext 那样直接调用 AbstractRefreshableApplicationContext的 refreshBeanFactory 去 初始化ioc容器。

这里调了BeanFactory,但是并没有创建BeanFactory的逻辑。

创建BeanFactory的逻辑在构造器。

public GenericApplicationContext() {
    this.beanFactory = new DefaultListableBeanFactory();
}

当创建上面三种上下文的时候,会执行父上下文 GenericApplicationContext 创建一个 DefaultListableBeanFactory 。

1.2、获得BeanFactory

//org.springframework.context.support.GenericApplicationContext#getBeanFactory
public final ConfigurableListableBeanFactory getBeanFactory() {
    return this.beanFactory;
}

2、初始化IOC

实际调用的是 AbstractApplicationContext#invokeBeanFactoryPostProcessors 方法,利用Spring的BeanFactory的后置处理器初始化IOC。

//org.springframework.context.support.AbstractApplicationContext#invokeBeanFactoryPostProcessors
protected void invokeBeanFactoryPostProcessors(ConfigurableListableBeanFactory beanFactory) {
    //调用Spring的BeanFactory后知处理器。
    PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(beanFactory, getBeanFactoryPostProcessors());

    // Detect a LoadTimeWeaver and prepare for weaving, if found in the meantime
    // (e.g. through an @Bean method registered by ConfigurationClassPostProcessor)
    if (beanFactory.getTempClassLoader() == null && beanFactory.containsBean(LOAD_TIME_WEAVER_BEAN_NAME)) {
        beanFactory.addBeanPostProcessor(new LoadTimeWeaverAwareProcessor(beanFactory));
        beanFactory.setTempClassLoader(new ContextTypeMatchClassLoader(beanFactory.getBeanClassLoader()));
    }
}

调用BeanFactory的后置处理器

//org.springframework.context.support.PostProcessorRegistrationDelegate#invokeBeanFactoryPostProcessors(org.springframework.beans.factory.config.ConfigurableListableBeanFactory, java.util.List<org.springframework.beans.factory.config.BeanFactoryPostProcessor>)
public static void invokeBeanFactoryPostProcessors(
			ConfigurableListableBeanFactory beanFactory, List<BeanFactoryPostProcessor> beanFactoryPostProcessors) {

    // Invoke BeanDefinitionRegistryPostProcessors first, if any.
    // 保存被处理过的bean的名称。
    Set<String> processedBeans = new HashSet<>();
	//beanFactory 是 DefaultListableBeanFactory ,实现了 BeanDefinitionRegistry
    if (beanFactory instanceof BeanDefinitionRegistry) {
        BeanDefinitionRegistry registry = (BeanDefinitionRegistry) beanFactory;
        List<BeanFactoryPostProcessor> regularPostProcessors = new ArrayList<>();
        List<BeanDefinitionRegistryPostProcessor> registryProcessors = new ArrayList<>();
		//调用 BeanFactoryPostProcessor 的 postProcessBeanDefinitionRegistry
        for (BeanFactoryPostProcessor postProcessor : beanFactoryPostProcessors) {
            if (postProcessor instanceof BeanDefinitionRegistryPostProcessor) {
                BeanDefinitionRegistryPostProcessor registryProcessor =
                    (BeanDefinitionRegistryPostProcessor) postProcessor;
                registryProcessor.postProcessBeanDefinitionRegistry(registry);
                registryProcessors.add(registryProcessor);
            }
            else {
                regularPostProcessors.add(postProcessor);
            }
        }
        //走到这里,registryProcessor 和 regularPostProcessors 分别是
        //registryProcessors 0 = {SharedMetadataReaderFactoryContextInitializer$CachingMetadataReaderFactoryPostProcessor} 
		//1 = {ConfigurationWarningsApplicationContextInitializer$ConfigurationWarningsPostProcessor} 
        //regularPostProcessors 0 = {ConfigFileApplicationListener$PropertySourceOrderingPostProcessor} 
        //registryProcessor 中的两个后知处理器执行了 postProcessBeanDefinitionRegistry 方法

        // Do not initialize FactoryBeans here: We need to leave all regular beans
        // uninitialized to let the bean factory post-processors apply to them!
        // Separate between BeanDefinitionRegistryPostProcessors that implement
        // PriorityOrdered, Ordered, and the rest.
        // 这里将BeanDefinitionRegistryPostProcessor 按 PriorityOrdered, Ordered, 和其他 区分
        List<BeanDefinitionRegistryPostProcessor> currentRegistryProcessors = new ArrayList<>();

        // First, invoke the BeanDefinitionRegistryPostProcessors that implement PriorityOrdered.
        // postProcessorNames = "org.springframework.context.annotation.internalConfigurationAnnotationProcessor"
        String[] postProcessorNames = 
beanFactory.getBeanNamesForType(BeanDefinitionRegistryPostProcessor.class, true, false);
        for (String ppName : postProcessorNames) {
            if (beanFactory.isTypeMatch(ppName, PriorityOrdered.class)) {
                currentRegistryProcessors.add(beanFactory.getBean(ppName, BeanDefinitionRegistryPostProcessor.class));
                processedBeans.add(ppName);
            }
        }
        //processedBeans = "org.springframework.context.annotation.internalConfigurationAnnotationProcessor"
        //currentRegistryProcessors = ConfigurationClassPostProcessor
        //排序
        sortPostProcessors(currentRegistryProcessors, beanFactory);
        registryProcessors.addAll(currentRegistryProcessors);
        // 现在 registryProcessors = {ArrayList@3018}  size = 3
		// 0 = {SharedMetadataReaderFactoryContextInitializer$CachingMetadataReaderFactoryPostProcessor@3019} 
		// 1 = {ConfigurationWarningsApplicationContextInitializer$ConfigurationWarningsPostProcessor@3042} 
		// 2 = {ConfigurationClassPostProcessor@3301} 
        //调用 BeanDefinitionRegistryPostProcessors
        // 这里currentRegistryProcessors = ConfigurationClassPostProcessor
        invokeBeanDefinitionRegistryPostProcessors(currentRegistryProcessors, registry);
        // currentRegistryProcessors 清空
        currentRegistryProcessors.clear();

        // Next, invoke the BeanDefinitionRegistryPostProcessors that implement Ordered.
        // 下面这一段调用 实现了 order 的 BeanDefinitionRegistryPostProcessors
        // postProcessorNames = "org.springframework.context.annotation.internalConfigurationAnnotationProcessor"
        postProcessorNames = beanFactory.getBeanNamesForType(BeanDefinitionRegistryPostProcessor.class, true, false);
        for (String ppName : postProcessorNames) {
            if (!processedBeans.contains(ppName) && beanFactory.isTypeMatch(ppName, Ordered.class)) {
                currentRegistryProcessors.add(beanFactory.getBean(ppName, BeanDefinitionRegistryPostProcessor.class));
                processedBeans.add(ppName);
            }
        }
        // processedBeans =  0 = "org.springframework.context.annotation.internalConfigurationAnnotationProcessor"
        sortPostProcessors(currentRegistryProcessors, beanFactory);
        registryProcessors.addAll(currentRegistryProcessors);
        // 现在 registryProcessors = {ArrayList@3018}  size = 3
		// 0 = {SharedMetadataReaderFactoryContextInitializer$CachingMetadataReaderFactoryPostProcessor@3019} 
		// 1 = {ConfigurationWarningsApplicationContextInitializer$ConfigurationWarningsPostProcessor@3042} 
		// 2 = {ConfigurationClassPostProcessor@3301} 
        //currentRegistryProcessors 为空
        invokeBeanDefinitionRegistryPostProcessors(currentRegistryProcessors, registry);
        currentRegistryProcessors.clear();

        // Finally, invoke all other BeanDefinitionRegistryPostProcessors until no further ones appear.
        // 调用所有其他的 BeanDefinitionRegistryPostProcessors
        // 这个循环里面没有任何操作。。。
        boolean reiterate = true;
        while (reiterate) {
            reiterate = false;
            //org.springframework.context.annotation.internalConfigurationAnnotationProcessor
            postProcessorNames = beanFactory.getBeanNamesForType(BeanDefinitionRegistryPostProcessor.class, true, false);
            for (String ppName : postProcessorNames) {
                // 这里是false
                if (!processedBeans.contains(ppName)) {
                    currentRegistryProcessors.add(beanFactory.getBean(ppName, BeanDefinitionRegistryPostProcessor.class));
                    processedBeans.add(ppName);
                    reiterate = true;
                }
            }
            sortPostProcessors(currentRegistryProcessors, beanFactory);
            registryProcessors.addAll(currentRegistryProcessors);
            // currentRegistryProcessors 为空
            invokeBeanDefinitionRegistryPostProcessors(currentRegistryProcessors, registry);
            currentRegistryProcessors.clear();
        }

        // Now, invoke the postProcessBeanFactory callback of all processors handled so far.
        // 调用所有 postProcessBeanFactory
        // registryProcessors = org.springframework.boot.autoconfigure.SharedMetadataReaderFactoryContextInitializer.CachingMetadataReaderFactoryPostProcessor,org.springframework.boot.context.ConfigurationWarningsApplicationContextInitializer.ConfigurationWarningsPostProcessor,org.springframework.context.annotation.ConfigurationClassPostProcessor
        invokeBeanFactoryPostProcessors(registryProcessors, beanFactory);
        //regularPostProcessors = org.springframework.boot.context.config.ConfigFileApplicationListener.PropertySourceOrderingPostProcessor
        invokeBeanFactoryPostProcessors(regularPostProcessors, beanFactory);
    }

    else {
        // Invoke factory processors registered with the context instance.
        invokeBeanFactoryPostProcessors(beanFactoryPostProcessors, beanFactory);
    }

    // Do not initialize FactoryBeans here: We need to leave all regular beans
    // uninitialized to let the bean factory post-processors apply to them!
    // 不初始化FactoryBeans 下面是 BeanFactoryPostProcessor
    //0 = "org.springframework.context.annotation.internalConfigurationAnnotationProcessor"
	//1 = "org.springframework.context.event.internalEventListenerProcessor"
	//2 = "propertySourcesPlaceholderConfigurer"
	//3 = "org.springframework.boot.context.properties.ConfigurationPropertiesBeanDefinitionValidator"
	//4 = "preserveErrorControllerTargetClassPostProcessor"
    String[] postProcessorNames =
        beanFactory.getBeanNamesForType(BeanFactoryPostProcessor.class, true, false);

    // Separate between BeanFactoryPostProcessors that implement PriorityOrdered,
    // Ordered, and the rest.
    //按 order 分为三个集合,优先级order,普通order,没有order
    List<BeanFactoryPostProcessor> priorityOrderedPostProcessors = new ArrayList<>();
    List<String> orderedPostProcessorNames = new ArrayList<>();
    List<String> nonOrderedPostProcessorNames = new ArrayList<>();
    for (String ppName : postProcessorNames) {
        if (processedBeans.contains(ppName)) {
            // skip - already processed in first phase above
        }
        else if (beanFactory.isTypeMatch(ppName, PriorityOrdered.class)) {
            priorityOrderedPostProcessors.add(beanFactory.getBean(ppName, BeanFactoryPostProcessor.class));
        }
        else if (beanFactory.isTypeMatch(ppName, Ordered.class)) {
            orderedPostProcessorNames.add(ppName);
        }
        else {
            nonOrderedPostProcessorNames.add(ppName);
        }
    }

    // First, invoke the BeanFactoryPostProcessors that implement PriorityOrdered.
    sortPostProcessors(priorityOrderedPostProcessors, beanFactory);
    //调用 实现优先级order 的 bean 的
    // priorityOrderedPostProcessors = {PropertySourcesPlaceholderConfigurer@4157} 
    invokeBeanFactoryPostProcessors(priorityOrderedPostProcessors, beanFactory);

    // Next, invoke the BeanFactoryPostProcessors that implement Ordered.
    List<BeanFactoryPostProcessor> orderedPostProcessors = new ArrayList<>(orderedPostProcessorNames.size());
    for (String postProcessorName : orderedPostProcessorNames) {
        orderedPostProcessors.add(beanFactory.getBean(postProcessorName, BeanFactoryPostProcessor.class));
    }
    sortPostProcessors(orderedPostProcessors, beanFactory);
    //调用 实现普通order 的 bean 的
    // orderedPostProcessors = {ConfigurationPropertiesBeanDefinitionValidator} 
    invokeBeanFactoryPostProcessors(orderedPostProcessors, beanFactory);

    // Finally, invoke all other BeanFactoryPostProcessors.
    // 调用其他 BeanFactoryPostProcessors
    List<BeanFactoryPostProcessor> nonOrderedPostProcessors = new ArrayList<>(nonOrderedPostProcessorNames.size());
    for (String postProcessorName : nonOrderedPostProcessorNames) {
        nonOrderedPostProcessors.add(beanFactory.getBean(postProcessorName, BeanFactoryPostProcessor.class));
    }
    //调用 没有实现order 的 bean 的
    //nonOrderedPostProcessors =  0 = {EventListenerMethodProcessor@4482} 
	// 1 = {ErrorMvcAutoConfiguration$PreserveErrorControllerTargetClassPostProcessor@4483} 
    invokeBeanFactoryPostProcessors(nonOrderedPostProcessors, beanFactory);

    // Clear cached merged bean definitions since the post-processors might have
    // modified the original metadata, e.g. replacing placeholders in values...
    beanFactory.clearMetadataCache();
}

上面这个大方法主要做了两件事,调用所有 BeanDefinitionRegistryPostProcessor 和 BeanFactoryPostProcessor 。

对于注解的扫描和处理,加载,注册,都在 org.springframework.context.annotation.ConfigurationClassPostProcessor#postProcessBeanDefinitionRegistry中。

其中BeanDefinitionRegistryPostProcessor 的有:

org.springframework.boot.autoconfigure.SharedMetadataReaderFactoryContextInitializer.CachingMetadataReaderFactoryPostProcessor,
org.springframework.boot.context.ConfigurationWarningsApplicationContextInitializer.ConfigurationWarningsPostProcessor,
org.springframework.context.annotation.ConfigurationClassPostProcessor

BeanFactoryPostProcessor 的有:

org.springframework.boot.autoconfigure.SharedMetadataReaderFactoryContextInitializer.CachingMetadataReaderFactoryPostProcessor,
org.springframework.boot.context.ConfigurationWarningsApplicationContextInitializer.ConfigurationWarningsPostProcessor,
org.springframework.context.annotation.ConfigurationClassPostProcessor

org.springframework.boot.context.config.ConfigFileApplicationListener.PropertySourceOrderingPostProcessor

org.springframework.context.support.PropertySourcesPlaceholderConfigurer
org.springframework.boot.context.properties.ConfigurationPropertiesBeanDefinitionValidator
org.springframework.context.event.EventListenerMethodProcessor
org.springframework.boot.autoconfigure.web.servlet.error.ErrorMvcAutoConfiguration$PreserveErrorControllerTargetClassPostProcessor

按照 order 分为

priorityOrderedPostProcessors = PropertySourcesPlaceholderConfigurer
orderedPostProcessors = ConfigurationPropertiesBeanDefinitionValidator
nonOrderedPostProcessors = EventListenerMethodProcessor,ErrorMvcAutoConfiguration$PreserveErrorControllerTargetClassPostProcessor

<think>我们正在讨论Spring Boot项目结构中应用上下文的生成机制和配置方法。根据引用内容,我们可以总结如下: 1. 在Spring Boot启动过程中,首先会触发`ApplicationEnvironmentPreparedEvent`事件(此时环境已准备就绪,但上下文尚未创建)[^1]。 2. Spring Boot底层仍然是SpringSpring MVC,但通过自动配置简化了配置[^2]。 3. Spring Boot内部定义了多个生命周期事件,位于`org.springframework.boot.context.event`包中[^3]。 4. 在Spring Boot项目中,`DispatcherServlet`的上下文(即子上下文)和根上下文(`AnnotationConfigServletWebServerApplicationContext`)实际上是同一个实例[^4]。 5. Spring Boot通过`@SpringBootApplication`注解(组合了`@ComponentScan`等注解)来初始化上下文Spring的注解处理工具能够解析这些注解[^5]。 下面详细解释应用上下文的生成机制和配置方法: ### 应用上下文的生成机制 1. **启动过程**: - Spring Boot应用启动时,首先会创建一个`SpringApplication`实例。 - 在`run()`方法执行过程中,会触发一系列事件,其中`ApplicationEnvironmentPreparedEvent`事件标志着环境准备完成,此时可以修改配置[^1]。 - 接着,Spring Boot会创建应用上下文。对于Web应用,默认使用`AnnotationConfigServletWebServerApplicationContext`作为应用上下文[^4]。 2. **上下文初始化**: - 应用上下文在创建后,会进行初始化。这个初始化过程包括: - 加载Bean定义:通过`@ComponentScan`扫描指定包下的组件(如`@Component`, `@Service`, `@Repository`, `@Controller`等)[^5]。 - 执行自动配置:通过`@EnableAutoConfiguration`(包含在`@SpringBootApplication`中)加载自动配置类。 - 在Web应用中,根上下文(Root Context)和DispatcherServlet的上下文实际上是同一个实例,即`AnnotationConfigServletWebServerApplicationContext`[^4]。这与传统的Spring MVC项目(父子上下文)不同。 3. **上下文设置**: -上下文会被存储到`ServletContext`中,属性名为`WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE`[^4]。 - `DispatcherServlet`会通过`ApplicationContextAware`接口获取到该上下文,并将其设置为自己的上下文。 ### 配置方法 1. **通过`application.properties`/`application.yml`配置**: - 这是最常用的配置方式,可以设置服务器端口、数据库连接等属性。 2. **通过Java配置类**: - 使用`@Configuration`注解定义配置类,在类中通过`@Bean`注解注册Bean。 - 使用`@Import`注解导入其他配置类。 3. **通过环境变量和命令行参数**: - Spring Boot支持通过环境变量和命令行参数覆盖配置。 4. **自定义事件监听器**: - 可以实现`ApplicationListener`接口来监听Spring Boot的生命周期事件,例如`ApplicationEnvironmentPreparedEvent`,在环境准备就绪时进行自定义配置[^1][^3]。 5. **自定义`ApplicationContextInitializer`**: - 通过实现`ApplicationContextInitializer`接口,可以在应用上下文初始化之前执行一些操作。需要在`META-INF/spring.factories`中注册: ```properties org.springframework.context.ApplicationContextInitializer=com.example.MyInitializer ``` 6. **使用`@SpringBootApplication`的`scanBasePackages`属性**: - 可以指定要扫描的包,例如:`@SpringBootApplication(scanBasePackages = "com.example")`。 7. **替换内嵌服务器**: - 如果需要使用不同的Web服务器(如Jetty代替Tomcat),可以通过排除Tomcat依赖并添加Jetty依赖来实现。 ### 代码示例 以下是一个简单的Spring Boot启动类示例: ```java @SpringBootApplication public class MyApplication { public static void main(String[] args) { SpringApplication.run(MyApplication.class, args); } } ``` ### 总结 Spring Boot应用上下文的生成机制主要依赖于启动过程中的事件触发和注解解析。默认情况下,Web应用使用`AnnotationConfigServletWebServerApplicationContext`作为统一的上下文。配置方式多样,包括属性文件、Java配置、环境变量等,同时支持通过事件监听器和初始化器进行扩展。 §§相关问题§§ 1. Spring Boot中如何自定义应用上下文初始化? 2. Spring Boot的事件机制有哪些关键事件? 3. 在Spring Boot中如何替换内嵌的Web服务器?</think>### Spring Boot应用上下文生成机制与配置方法 #### 1. **上下文生成机制** Spring Boot应用上下文生成的核心流程如下: 1. **环境准备阶段** 触发`ApplicationEnvironmentPreparedEvent`事件,此时`ConfigurableEnvironment`已就绪但上下文尚未创建[^1]。这是修改默认配置或添加额外配置的关键时机(如引导上下文初始化)。 2. **上下文创建阶段** Spring Boot根据应用类型自动创建对应的应用上下文- **Web应用**:`AnnotationConfigServletWebServerApplicationContext`(默认) - **非Web应用**:`AnnotationConfigApplicationContext` ```mermaid graph LR A[SpringApplication.run] --> B{检测应用类型} B -->|Web应用| C[创建AnnotationConfigServletWebServerApplicationContext] B -->|非Web应用| D[创建AnnotationConfigApplicationContext] ``` 3. **上下文初始化** 通过`@SpringBootApplication`注解触发: - **组件扫描**:自动扫描`@Component`、`@Service`等注解 - **自动配置**:加载`META-INF/spring.factories`中的自动配置类 - **Bean注册**:解析`@Bean`注解的方法 4. **父子上下文关系** 在Web应用中: - **根上下文**:`AnnotationConfigServletWebServerApplicationContext`(存储到`ServletContext`) - **DispatcherServlet上下文**:与根上下文共享同一实例[^4] ```java // 上下文存储到ServletContext servletContext.setAttribute( WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE, this ); ``` #### 2. **关键配置方法 ##### (1) 显式配置上下文 ```java // 自定义应用上下文 public static void main(String[] args) { SpringApplication app = new SpringApplication(MyApp.class); app.setApplicationContextClass(MyCustomContext.class); // 指定上下文实现 app.run(args); } ``` ##### (2) 环境配置干预 ```java // 监听环境准备事件 @Bean public ApplicationListener<ApplicationEnvironmentPreparedEvent> envListener() { return event -> { ConfigurableEnvironment env = event.getEnvironment(); env.getPropertySources().addFirst(new MyCustomPropertySource()); }; } ``` ##### (3) 组件扫描配置 ```java @SpringBootApplication(scanBasePackages = "com.example.custom") public class MyApp { ... } ``` ##### (4) 上下文后置处理 ```java @Bean public ApplicationContextInitializer<ConfigurableApplicationContext> ctxInitializer() { return ctx -> { ctx.getBeanFactory().registerSingleton("myBean", new CustomBean()); }; } ``` #### 3. **生命周期事件 Spring Boot通过事件驱动上下文生命周期[^3]: 1. `ApplicationStartingEvent`:启动最初阶段 2. `ApplicationEnvironmentPreparedEvent`:环境就绪 3. `ApplicationContextInitializedEvent`:上下文初始化完成 4. `ApplicationPreparedEvent`:Bean定义加载完成 5. `ApplicationStartedEvent`:上下文刷新完成 #### 4. 调试技巧 查看当前上下文类型: ```java @SpringBootApplication public class MyApp implements ApplicationRunner { public static void main(String[] args) { SpringApplication.run(MyApp.class, args); } @Override public void run(ApplicationArguments args) { ApplicationContext ctx = SpringApplication.run(MyApp.class, args); System.out.println("Context type: " + ctx.getClass().getName()); } } // 输出:org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext ``` ### 总结 Spring Boot通过智能默认配置简化了上下文创建: 1. 基于`spring-boot-autoconfigure`自动检测应用类型 2. 通过`@SpringBootApplication`组合注解触发组件扫描和配置 3. 使用统一上下文模型简化Web应用结构[^4][^5] 4. 提供丰富的事件扩展点供开发者干预生命周期
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值