What is the underlying startup process of Springboot?
SpringApplication construction analysis
1. Record BeanDefinition source
The spring container is empty at the beginning. Go to various sources to find the beanDefinition. These sources may be configuration classes or xml files. In the construction method, a main source will be obtained, which is the bootstrap class, and the beanDefinition will be obtained according to the bootstrap class.
2. Infer the application type
Determine the reference type based on the jar package
3. Record the ApplicationContext initializer
Expand the ApplicationContext
4. Record listener
Listen to important events
5. Infer the main startup class
Record the running main class.
SpringApplication run analysis
1. Get SpringApplicationRunListeners. The name is not obtained well. It is actually an event publisher
Publishes the application starting event and publishes the event at important nodes when the program starts
public static void main(String[] args) throws Exception{ // 添加 app 监听器 SpringApplication app = new SpringApplication(); app.addListeners(e -> System.out.println(e.getClass())); // 获取事件发送器实现类名 List<String> names = SpringFactoriesLoader.loadFactoryNames(SpringApplicationRunListener.class, A39_2.class.getClassLoader()); for (String name : names) { System.out.println(name); Class<?> clazz = Class.forName(name); Constructor<?> constructor = clazz.getConstructor(SpringApplication.class, String[].class); SpringApplicationRunListener publisher = (SpringApplicationRunListener) constructor.newInstance(app, args); // 发布事件 DefaultBootstrapContext bootstrapContext = new DefaultBootstrapContext(); publisher.starting(bootstrapContext); // spring boot 开始启动 publisher.environmentPrepared(bootstrapContext, new StandardEnvironment()); // 环境信息准备完毕 GenericApplicationContext context = new GenericApplicationContext(); publisher.contextPrepared(context); // 在 spring 容器创建,并调用初始化器之后,发送此事件 publisher.contextLoaded(context); // 所有 bean definition 加载完毕 context.refresh(); publisher.started(context); // spring 容器初始化完成(refresh 方法调用完毕) publisher.running(context); // spring boot 启动完毕 publisher.failed(context, new Exception("出错了")); // spring boot 启动出错 }
2. Encapsulate startup args
3. Prepare Environment to add command line parameters (*)
public static void main(String[] args) throws IOException { ApplicationEnvironment env = new ApplicationEnvironment(); // 系统环境变量, properties, yaml env.getPropertySources().addLast(new ResourcePropertySource(new ClassPathResource("step3.properties"))); env.getPropertySources().addFirst(new SimpleCommandLinePropertySource(args)); for (PropertySource<?> ps : env.getPropertySources()) { System.out.println(ps); } // System.out.println(env.getProperty("JAVA_HOME")); System.out.println(env.getProperty("server.port")); }
4. ConfigurationPropertySources processing (*)
Publish application environment has prepared events
public static void main(String[] args) throws IOException, NoSuchFieldException { ApplicationEnvironment env = new ApplicationEnvironment(); env.getPropertySources().addLast( new ResourcePropertySource("step4", new ClassPathResource("step4.properties")) ); ConfigurationPropertySources.attach(env); for (PropertySource<?> ps : env.getPropertySources()) { System.out.println(ps); } System.out.println(env.getProperty("user.first-name")); System.out.println(env.getProperty("user.middle-name")); System.out.println(env.getProperty("user.last-name")); } }
5. Env post-processing (*) through EnvironmentPostProcessorApplicationListener
application.properties, parsed by StandardConfigDataLocationResolver
spring.application.json
public class Step5 { public static void main(String[] args) { SpringApplication app = new SpringApplication(); app.addListeners(new EnvironmentPostProcessorApplicationListener()); /*List<String> names = SpringFactoriesLoader.loadFactoryNames(EnvironmentPostProcessor.class, Step5.class.getClassLoader()); for (String name : names) { System.out.println(name); }*/ EventPublishingRunListener publisher = new EventPublishingRunListener(app, args); ApplicationEnvironment env = new ApplicationEnvironment(); System.out.println(">>>>>>>>>>>>>>>>>>>>>>>>> 增强前"); for (PropertySource<?> ps : env.getPropertySources()) { System.out.println(ps); } publisher.environmentPrepared(new DefaultBootstrapContext(), env); System.out.println(">>>>>>>>>>>>>>>>>>>>>>>>> 增强后"); for (PropertySource<?> ps : env.getPropertySources()) { System.out.println(ps); } } private static void test1() { SpringApplication app = new SpringApplication(); ApplicationEnvironment env = new ApplicationEnvironment(); System.out.println(">>>>>>>>>>>>>>>>>>>>>>>>> 增强前"); for (PropertySource<?> ps : env.getPropertySources()) { System.out.println(ps); } ConfigDataEnvironmentPostProcessor postProcessor1 = new ConfigDataEnvironmentPostProcessor(new DeferredLogs(), new DefaultBootstrapContext()); postProcessor1.postProcessEnvironment(env, app); System.out.println(">>>>>>>>>>>>>>>>>>>>>>>>> 增强后"); for (PropertySource<?> ps : env.getPropertySources()) { System.out.println(ps); } RandomValuePropertySourceEnvironmentPostProcessor postProcessor2 = new RandomValuePropertySourceEnvironmentPostProcessor(new DeferredLog()); postProcessor2.postProcessEnvironment(env, app); System.out.println(">>>>>>>>>>>>>>>>>>>>>>>>> 增强后"); for (PropertySource<?> ps : env.getPropertySources()) { System.out.println(ps); } System.out.println(env.getProperty("server.port")); System.out.println(env.getProperty("random.int")); System.out.println(env.getProperty("random.int")); System.out.println(env.getProperty("random.int")); System.out.println(env.getProperty("random.uuid")); System.out.println(env.getProperty("random.uuid")); System.out.println(env.getProperty("random.uuid")); } }
6. Bind spring.main to the SpringApplication object (*)
Assign the value in the configuration file to the default attribute value of SpringApplication
public class Step6 { // 绑定 spring.main 前缀的 key value 至 SpringApplication, 请通过 debug 查看 public static void main(String[] args) throws IOException { SpringApplication application = new SpringApplication(); ApplicationEnvironment env = new ApplicationEnvironment(); env.getPropertySources().addLast(new ResourcePropertySource("step6", new ClassPathResource("step6.properties"))); System.out.println(application); Binder.get(env).bind("spring.main", Bindable.ofInstance(application)); System.out.println(application); }
7. Print banner (*)
public class Step7 { public static void main(String[] args) { ApplicationEnvironment env = new ApplicationEnvironment(); SpringApplicationBannerPrinter printer = new SpringApplicationBannerPrinter( new DefaultResourceLoader(), new SpringBootBanner() ); // 测试文字 banner // env.getPropertySources().addLast(new MapPropertySource("custom", Map.of("spring.banner.location","banner1.txt"))); // 测试图片 banner // env.getPropertySources().addLast(new MapPropertySource("custom", Map.of("spring.banner.image.location","banner2.png"))); // 版本号的获取 System.out.println(SpringBootVersion.getVersion()); printer.print(env, Step7.class, System.out); } }
8. Create container
private static GenericApplicationContext createApplicationContext(WebApplicationType type) { GenericApplicationContext context = null; switch (type) { case SERVLET -> context = new AnnotationConfigServletWebServerApplicationContext(); case REACTIVE -> context = new AnnotationConfigReactiveWebServerApplicationContext(); case NONE -> context = new AnnotationConfigApplicationContext(); } return context; }
9. Prepare container release
application context initialized event
10.Load bean definition
Publish application prepared event
DefaultListableBeanFactory beanFactory = context.getDefaultListableBeanFactory(); AnnotatedBeanDefinitionReader reader1 = new AnnotatedBeanDefinitionReader(beanFactory); XmlBeanDefinitionReader reader2 = new XmlBeanDefinitionReader(beanFactory); ClassPathBeanDefinitionScanner scanner = new ClassPathBeanDefinitionScanner(beanFactory); reader1.register(Config.class); reader2.loadBeanDefinitions(new ClassPathResource("b03.xml")); scanner.scan("com.itheima.a39.sub");
11, refresh container
Publish application started event
12, execute runner
Publish application ready Event
There is an exception, please publish application failed event
The above is the detailed content of What is the underlying startup process of Springboot?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Introduction to Jasypt Jasypt is a java library that allows a developer to add basic encryption functionality to his/her project with minimal effort and does not require a deep understanding of how encryption works. High security for one-way and two-way encryption. , standards-based encryption technology. Encrypt passwords, text, numbers, binaries... Suitable for integration into Spring-based applications, open API, for use with any JCE provider... Add the following dependency: com.github.ulisesbocchiojasypt-spring-boot-starter2. 1.1Jasypt benefits protect our system security. Even if the code is leaked, the data source can be guaranteed.

1. Redis implements distributed lock principle and why distributed locks are needed. Before talking about distributed locks, it is necessary to explain why distributed locks are needed. The opposite of distributed locks is stand-alone locks. When we write multi-threaded programs, we avoid data problems caused by operating a shared variable at the same time. We usually use a lock to mutually exclude the shared variables to ensure the correctness of the shared variables. Its scope of use is in the same process. If there are multiple processes that need to operate a shared resource at the same time, how can they be mutually exclusive? Today's business applications are usually microservice architecture, which also means that one application will deploy multiple processes. If multiple processes need to modify the same row of records in MySQL, in order to avoid dirty data caused by out-of-order operations, distribution needs to be introduced at this time. The style is locked. Want to achieve points

Usage scenario 1. The order was placed successfully but the payment was not made within 30 minutes. The payment timed out and the order was automatically canceled. 2. The order was signed and no evaluation was conducted for 7 days after signing. If the order times out and is not evaluated, the system defaults to a positive rating. 3. The order is placed successfully. If the merchant does not receive the order for 5 minutes, the order is cancelled. 4. The delivery times out, and push SMS reminder... For scenarios with long delays and low real-time performance, we can Use task scheduling to perform regular polling processing. For example: xxl-job Today we will pick

Springboot reads the file, but cannot access the latest development after packaging it into a jar package. There is a situation where springboot cannot read the file after packaging it into a jar package. The reason is that after packaging, the virtual path of the file is invalid and can only be accessed through the stream. Read. The file is under resources publicvoidtest(){Listnames=newArrayList();InputStreamReaderread=null;try{ClassPathResourceresource=newClassPathResource("name.txt");Input

SpringBoot and SpringMVC are both commonly used frameworks in Java development, but there are some obvious differences between them. This article will explore the features and uses of these two frameworks and compare their differences. First, let's learn about SpringBoot. SpringBoot was developed by the Pivotal team to simplify the creation and deployment of applications based on the Spring framework. It provides a fast, lightweight way to build stand-alone, executable

1. Customize RedisTemplate1.1, RedisAPI default serialization mechanism. The API-based Redis cache implementation uses the RedisTemplate template for data caching operations. Here, open the RedisTemplate class and view the source code information of the class. publicclassRedisTemplateextendsRedisAccessorimplementsRedisOperations, BeanClassLoaderAware{//Declare key, Various serialization methods of value, the initial value is empty @NullableprivateRedisSe

When Springboot+Mybatis-plus does not use SQL statements to perform multi-table adding operations, the problems I encountered are decomposed by simulating thinking in the test environment: Create a BrandDTO object with parameters to simulate passing parameters to the background. We all know that it is extremely difficult to perform multi-table operations in Mybatis-plus. If you do not use tools such as Mybatis-plus-join, you can only configure the corresponding Mapper.xml file and configure The smelly and long ResultMap, and then write the corresponding sql statement. Although this method seems cumbersome, it is highly flexible and allows us to

In projects, some configuration information is often needed. This information may have different configurations in the test environment and the production environment, and may need to be modified later based on actual business conditions. We cannot hard-code these configurations in the code. It is best to write them in the configuration file. For example, you can write this information in the application.yml file. So, how to get or use this address in the code? There are 2 methods. Method 1: We can get the value corresponding to the key in the configuration file (application.yml) through the ${key} annotated with @Value. This method is suitable for situations where there are relatively few microservices. Method 2: In actual projects, When business is complicated, logic
