How Spring Boot Auto‑Configuration Works: Inside @SpringBootApplication and @EnableAutoConfiguration

Introduction

Spring Boot’s popularity stems from its ability to start projects with minimal configuration, largely thanks to its auto‑configuration system. This article explores the underlying source code to reveal how annotations such as @SpringBootApplication, @EnableAutoConfiguration, and related mechanisms make this possible.

Source Version

The analysis targets Spring Boot 2.4.0. Readers should align their code with this version to avoid discrepancies caused by changes in later releases.

What @SpringBootApplication Does

The annotation itself is a composite of three other annotations: @SpringBootConfiguration – essentially @Configuration, allowing the main class to define beans. @EnableAutoConfiguration – activates Spring Boot’s auto‑configuration feature. @ComponentScan – enables package scanning for components.

Thus, the real work lies in @EnableAutoConfiguration, which the article examines in depth.

What @EnableAutoConfiguration Does

The annotation imports two critical pieces: @AutoConfigurationPackage – automatically registers the package of the class annotated with @SpringBootApplication (and its sub‑packages) for component scanning. @Import(AutoConfigurationImportSelector.class) – brings in the selector that loads auto‑configuration classes.

@AutoConfigurationPackage

This annotation imports AutoConfigurationPackages.Registrar, whose registerBeanDefinitions method determines the base packages to scan. The package list is built from two sources: the packages declared in @AutoConfigurationPackage itself and the package where the annotation resides (i.e., the package of the main class).

@Import(AutoConfigurationImportSelector.class)

The selector implements DeferredImportSelector, which changes the import timing compared to a regular ImportSelector. Its core logic resides in the process() method, which delegates to getAutoConfigurationEntry() to collect auto‑configuration candidates.

The selector reads META-INF/spring.factories to obtain a list of auto‑configuration classes, then removes any classes explicitly excluded via @SpringBootApplication ’s exclude attribute.

The spring.factories file in the spring-boot-autoconfigure module lists dozens of auto‑configuration classes, such as EnableAutoConfiguration, AopAutoConfiguration, RabbitAutoConfiguration, and many others, which are conditionally applied based on classpath presence and property settings.

# Auto Configure
org.springframework.boot.autoconfigure.EnableAutoConfiguration=\
org.springframework.boot.autoconfigure.admin.SpringApplicationAdminJmxAutoConfiguration,\
org.springframework.boot.autoconfigure.aop.AopAutoConfiguration,\
org.springframework.boot.autoconfigure.amqp.RabbitAutoConfiguration,\
org.springframework.boot.autoconfigure.batch.BatchAutoConfiguration,\
... (truncated for brevity)

Conclusion

The article demonstrates that Spring Boot’s “magic” is a well‑structured series of annotations and import selectors that read configuration metadata, scan packages, and load auto‑configuration classes from spring.factories. Understanding this flow enables developers to customize or extend the auto‑configuration process effectively.