search
HomeJavajavaTutorialSpringBoot execution process example analysis

SpringBoot execution process example analysis

May 12, 2023 pm 03:19 PM
springboot

Each Spring Boot project has a main program startup class. In the main program startup class, there is a main() method to start the project. In this method, the entire Spring Boot program can be started by executing SpringApplication.run() .

Question: So how does the SpringApplication.run() method start the Spring Boot project?

Let’s look at the source code inside the run() method. The core code is as follows:

@SpringBootApplication
public class SpringbootDemoApplication {
    public static void main(String[] args) {
        SpringApplication.run(SpringbootDemoApplication.class, args);
    }
}
public static ConfigurableApplicationContext run(Class<?> primarySource, String... args) {
    return run(new Class[]{primarySource}, args);
}
    public static ConfigurableApplicationContext run(Class<?>[] primarySources, String[] args) {
        return (new SpringApplication(primarySources)).run(args);
}

As can be seen from the above source code, the SpringApplication.run() method performs two operations, respectively. It is the initial creation of the SpringApplication instance and calling run() to start the project. The implementation of these two stages is detailed as follows

1. Initial creation of SpringApplication instance

View the source code information of initialization and creation of SpringApplication instance object. The core code is as follows

    public SpringApplication(ResourceLoader resourceLoader, Class... primarySources) {
        this.sources = new LinkedHashSet();
        this.bannerMode = Mode.CONSOLE;
        this.logStartupInfo = true;
        this.addCommandLineProperties = true;
        this.addConversionService = true;
        this.headless = true;
        this.registerShutdownHook = true;
        this.additionalProfiles = new HashSet();
        this.isCustomEnvironment = false;
        this.resourceLoader = resourceLoader;
        Assert.notNull(primarySources, "PrimarySources must not be null");
    // 把项目启动类.class设置为属性存储起来
        this.primarySources = new LinkedHashSet(Arrays.asList(primarySources));
    // 判断当前webApplicationType应用的类型
        this.webApplicationType = WebApplicationType.deduceFromClasspath();
    // 设置初始化器(Initializer),最后会调用这些初始化器
        this.setInitializers(this.getSpringFactoriesInstances(ApplicationContextInitializer.class));
    // 设置监听器(Listener)
        this.setListeners(this.getSpringFactoriesInstances(ApplicationListener.class));
    // 用于推断并设置项目main()方法启动的主程序启动类
        this.mainApplicationClass = this.deduceMainApplicationClass();

As can be seen from the above source code, the initialization process of SpringApplication mainly includes 4 parts, detailed description as follows.

(1) this.webApplicationType = WebApplicationType.deduceFromClasspath()

is used to determine the type of the current webApplicationType application. The deduceFromClasspath() method is used to check whether a certain feature class exists under the Classpath class path, so as to determine whether the current webApplicationType type is a SERVLET application (traditional MVC application before Spring 5) or a REACTIVE application (WebFlux interactive application that began to appear in Spring 5)

(2) this.setInitializers(this.getSpringFactoriesInstances(ApplicationContextInitializer.class))

Initializer settings for SpringApplication applications. During the initializer setting process, the Spring class loader SpringFactoriesLoader will be used to obtain all available application initializer classes ApplicationContextInitializer from the spring.factores file under META-INF under the META-INF/spring.factories class path.

(3) this.setListeners(this.getSpringFactoriesInstances(ApplicationListener.class))

Used for listener settings of SpringApplication application. The listener setting process is basically the same as the initializer setting process in the previous step. SpringFactoriesLoader is also used to obtain all available listener classes ApplicationListener from the spring.factores file under META-INF under the META-INF/spring.factories class path.

(4) this.mainApplicationClass = this.deduceMainApplicationClass()

Used to infer and set the main program startup class started by the project main() method

2. Initialization startup of the project

After analyzing the initialization and creation of the SpringApplication instance object in the previous part of the (new SpringApplication(primarySources)).run(args) source code, check the project initialization startup process and core code executed by the run(args) method The details are as follows:

  public ConfigurableApplicationContext run(String... args) {
        StopWatch stopWatch = new StopWatch();
        stopWatch.start();
        ConfigurableApplicationContext context = null;
        Collection<SpringBootExceptionReporter> exceptionReporters = new ArrayList();
        this.configureHeadlessProperty();
    // 第一步:获取并启动监听器
        SpringApplicationRunListeners listeners = this.getRunListeners(args);
        listeners.starting();
        Collection exceptionReporters;
        try {
            ApplicationArguments applicationArguments = new DefaultApplicationArguments(args);
    // 第二步:根据SpringApplicationRunListeners以及参数来准备环境
            ConfigurableEnvironment environment = this.prepareEnvironment(listeners, applicationArguments);
            this.configureIgnoreBeanInfo(environment);
    // 准备Banner打印器 - 就是启动Spring Boot的时候打印在console上的ASCII艺术字体
            Banner printedBanner = this.printBanner(environment);
    // 第三步:创建Spring容器
            context = this.createApplicationContext();
            exceptionReporters = this.getSpringFactoriesInstances(SpringBootExceptionReporter.class, new Class[]{ConfigurableApplicationContext.class}, new Object[]{context});
    // 第四步:Spring容器前置处理
            this.prepareContext(context, environment, listeners, applicationArguments, printedBanner);
    // 第五步:刷新容器
            this.refreshContext(context);
    // 第六步:Spring容器后置处理
            this.afterRefresh(context, applicationArguments);
            stopWatch.stop();
            if (this.logStartupInfo) {
                (new StartupInfoLogger(this.mainApplicationClass)).logStarted(this.getApplicationLog(), stopWatch);
            }
    // 第七步:发出结束执行的事件
            listeners.started(context);
    // 返回容器
            this.callRunners(context, applicationArguments);
        } catch (Throwable var10) {
            this.handleRunFailure(context, var10, exceptionReporters, listeners);
            throw new IllegalStateException(var10);
        }
        try {
            listeners.running(context);
            return context;
        } catch (Throwable var9) {
            this.handleRunFailure(context, var9, exceptionReporters, (SpringApplicationRunListeners) null);
            throw new IllegalStateException(var9);
        }
    }

As can be seen from the above source code, the project initialization startup process generally includes the following parts:

Step 1: Obtain and start the listener

this.getRunListeners (args) and listeners.starting() methods are mainly used to obtain and run the SpringApplicationRunListener listener initialized during the SpringApplication instance initialization process.

Second step: Prepare the environment based on SpringApplicationRunListeners and parameters

This.prepareEnvironment(listeners, applicationArguments) method is mainly used to preset the project running environment, and at the same time, through this.configureIgnoreBeanInfo(environment ) method to exclude some unnecessary running environments

Step 3: Create a Spring container

Judge based on webApplicationType to determine the container type. If the type is a SERVLET type, the corresponding container will be loaded through reflection Bytecode, that is, AnnotationConfigServletWebServerApplicationContext, and then use the previously initialized context (application context environment), environment (project running environment), listeners (running listeners), applicationArguments (project parameters) and printedBanner (project icon information) to create the application context Assemble the configuration and refresh the configuration

Step 4: Spring container pre-processing

This step is mainly a preparatory action before the container is refreshed. Set up the container environment, including various variables, etc., which includes a very critical operation: injecting the startup class into the container to lay the foundation for subsequent automated configuration

Step 5: Refresh the container

Start refreshing the spring container, initialize the entire IOC container through the refresh method (including bean resource positioning, parsing, registration, etc.), and register a shutdown hook with the JVM runtime. This context will be closed when the JVM is shut down, unless it is at that time Already closed

Step 6: Spring container post-processing

Extension interface, template method in design mode, defaults to empty implementation. If you have custom requirements, you can override this method. For example, printing some startup and completion logs, or some other post-processing.

Step 7: Issue an event that ends execution

Get the EventPublishingRunListener listener and execute its started method, and pass the created Spring container in, create an ApplicationStartedEvent event, and execute ConfigurableApplicationContext The

publishEvent method, that is to say, the event is published in the Spring container, not in SpringApplication. This is different from the previous starting. The previous starting is published directly to the listener in SpringApplication. Start event.

Step 8: Execute Runners

Used to call the custom executor XxxRunner class in the project to execute some specific programs immediately after the project is started. Among them, the executor interfaces provided by Spring Boot include ApplicationRunner and CommandLineRunner. When using it, you only need to customize an executor class to implement one of the interfaces and rewrite the corresponding run() method interface. Then the Spring Boot project will be started immediately. Execute these specific programs

Below, through a Spring Boot execution flow chart, let everyone know more clearly the overall execution process and main startup stages of Spring Boot:

SpringBoot execution process example analysis

The above is the detailed content of SpringBoot execution process example analysis. For more information, please follow other related articles on the PHP Chinese website!

Statement
This article is reproduced at:亿速云. If there is any infringement, please contact admin@php.cn delete
How does platform independence benefit enterprise-level Java applications?How does platform independence benefit enterprise-level Java applications?May 03, 2025 am 12:23 AM

Java is widely used in enterprise-level applications because of its platform independence. 1) Platform independence is implemented through Java virtual machine (JVM), so that the code can run on any platform that supports Java. 2) It simplifies cross-platform deployment and development processes, providing greater flexibility and scalability. 3) However, it is necessary to pay attention to performance differences and third-party library compatibility and adopt best practices such as using pure Java code and cross-platform testing.

What role does Java play in the development of IoT (Internet of Things) devices, considering platform independence?What role does Java play in the development of IoT (Internet of Things) devices, considering platform independence?May 03, 2025 am 12:22 AM

JavaplaysasignificantroleinIoTduetoitsplatformindependence.1)Itallowscodetobewrittenonceandrunonvariousdevices.2)Java'secosystemprovidesusefullibrariesforIoT.3)ItssecurityfeaturesenhanceIoTsystemsafety.However,developersmustaddressmemoryandstartuptim

Describe a scenario where you encountered a platform-specific issue in Java and how you resolved it.Describe a scenario where you encountered a platform-specific issue in Java and how you resolved it.May 03, 2025 am 12:21 AM

ThesolutiontohandlefilepathsacrossWindowsandLinuxinJavaistousePaths.get()fromthejava.nio.filepackage.1)UsePaths.get()withSystem.getProperty("user.dir")andtherelativepathtoconstructthefilepath.2)ConverttheresultingPathobjecttoaFileobjectifne

What are the benefits of Java's platform independence for developers?What are the benefits of Java's platform independence for developers?May 03, 2025 am 12:15 AM

Java'splatformindependenceissignificantbecauseitallowsdeveloperstowritecodeonceandrunitonanyplatformwithaJVM.This"writeonce,runanywhere"(WORA)approachoffers:1)Cross-platformcompatibility,enablingdeploymentacrossdifferentOSwithoutissues;2)Re

What are the advantages of using Java for web applications that need to run on different servers?What are the advantages of using Java for web applications that need to run on different servers?May 03, 2025 am 12:13 AM

Java is suitable for developing cross-server web applications. 1) Java's "write once, run everywhere" philosophy makes its code run on any platform that supports JVM. 2) Java has a rich ecosystem, including tools such as Spring and Hibernate, to simplify the development process. 3) Java performs excellently in performance and security, providing efficient memory management and strong security guarantees.

How does the JVM contribute to Java's 'write once, run anywhere' (WORA) capability?How does the JVM contribute to Java's 'write once, run anywhere' (WORA) capability?May 02, 2025 am 12:25 AM

JVM implements the WORA features of Java through bytecode interpretation, platform-independent APIs and dynamic class loading: 1. Bytecode is interpreted as machine code to ensure cross-platform operation; 2. Standard API abstract operating system differences; 3. Classes are loaded dynamically at runtime to ensure consistency.

How do newer versions of Java address platform-specific issues?How do newer versions of Java address platform-specific issues?May 02, 2025 am 12:18 AM

The latest version of Java effectively solves platform-specific problems through JVM optimization, standard library improvements and third-party library support. 1) JVM optimization, such as Java11's ZGC improves garbage collection performance. 2) Standard library improvements, such as Java9's module system reducing platform-related problems. 3) Third-party libraries provide platform-optimized versions, such as OpenCV.

Explain the process of bytecode verification performed by the JVM.Explain the process of bytecode verification performed by the JVM.May 02, 2025 am 12:18 AM

The JVM's bytecode verification process includes four key steps: 1) Check whether the class file format complies with the specifications, 2) Verify the validity and correctness of the bytecode instructions, 3) Perform data flow analysis to ensure type safety, and 4) Balancing the thoroughness and performance of verification. Through these steps, the JVM ensures that only secure, correct bytecode is executed, thereby protecting the integrity and security of the program.

See all articles

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

EditPlus Chinese cracked version

EditPlus Chinese cracked version

Small size, syntax highlighting, does not support code prompt function

SublimeText3 Linux new version

SublimeText3 Linux new version

SublimeText3 Linux latest version

mPDF

mPDF

mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

Dreamweaver Mac version

Dreamweaver Mac version

Visual web development tools