部署SpringBoot到外部Tomcat为何需继承SpringBootServletInitializer？

Great question—this trips up a lot of developers when they first move from embedded to external Tomcat, so let’s break this down clearly.

First, Let’s Recap Embedded Tomcat Behavior #

When you run a Spring Boot app with its built-in embedded Tomcat (the default setup), your main() method is the entry point. Here’s what happens under the hood:

• You call SpringApplication.run(YourApplication.class, args)
• Spring Boot takes full control: it fires up the embedded Tomcat server, configures the Spring application context, registers servlets/filters, and wires all your beans automatically.
• No need for SpringBootServletInitializer here because Spring Boot is orchestrating the entire startup process from start to finish.

External Tomcat Works Differently #

When you deploy a Spring Boot war file to an external Tomcat, the Tomcat server starts first, not your Spring Boot app. Tomcat follows the Servlet specification, which means it needs a clear way to initialize your web application's context.

This is exactly why SpringBootServletInitializer is mandatory here:

• It implements Spring’s WebApplicationInitializer interface, which replaces the old web.xml setup for modern Servlet 3.0+ containers.
• When Tomcat boots up, it scans all classes implementing WebApplicationInitializer and triggers their onStartup() method.
• By extending SpringBootServletInitializer, you override the configure() method to tell Tomcat how to bootstrap your Spring Boot app. Here’s a typical example:

@SpringBootApplication
public class YourApplication extends SpringBootServletInitializer {
    @Override
    protected SpringApplicationBuilder configure(SpringApplicationBuilder application) {
        return application.sources(YourApplication.class);
    }

    public static void main(String[] args) {
        SpringApplication.run(YourApplication.class, args);
    }
}

• This method acts as a bridge between Tomcat’s Servlet container startup flow and Spring Boot’s application context initialization. Without it, Tomcat would deploy your war file but have no clue how to start your Spring Boot app—you’d end up with an empty, uninitialized web context.

The Core Difference Summarized #

• Embedded Tomcat: Spring Boot is in charge—it starts the server and initializes itself. No extra setup required.
• External Tomcat: Tomcat is in charge—it needs explicit instructions to fire up your Spring Boot app. SpringBootServletInitializer provides those instructions by hooking into Tomcat’s startup lifecycle.

内容的提问来源于stack exchange，提问作者Mehraj Malik