How Spring Boot Auto‑Configuration Works: Deep Dive into @EnableAutoConfiguration

1. Core Runtime Principle

Spring Boot’s core feature is auto‑configuration based on “convention over configuration”. When a starter is on the classpath, Spring Boot automatically loads related dependencies, reads spring.factories, and registers the appropriate AutoConfiguration classes.

2. Key Annotations and Files

@EnableAutoConfiguration : introduced via @SpringBootApplication, scans spring.factories and loads registered auto‑configuration classes.

spring.factories : located in META-INF, lists auto‑configuration classes.

AutoConfiguration classes : classes named *AutoConfiguration that define beans and conditions.

@Conditional : condition annotations that guard the instantiation of auto‑configuration classes.

Starters : dependency bundles that bring in required libraries and configuration.

3. @SpringBootApplication and Its Members

Typical Spring Boot projects generate an entry class named DemoApplication with a main method that calls SpringApplication.run(...). The class is annotated with @SpringBootApplication, which itself combines @SpringBootConfiguration, @EnableAutoConfiguration, and @ComponentScan.

@SpringBootApplication
public class SpringLearnApplication {
    public static void main(String[] args) {
        SpringApplication.run(DemoApplication.class, args);
    }
}

The annotation defines several alias attributes such as exclude, excludeName, scanBasePackages, scanBasePackageClasses, and proxyBeanMethods. The proxyBeanMethods flag controls CGLIB subclass generation for @Configuration classes.

4. @EnableAutoConfiguration Source

@Target(ElementType.TYPE)
@Retention(RetentionPolicy.RUNTIME)
@Documented
@Inherited
@AutoConfigurationPackage
@Import(AutoConfigurationImportSelector.class)
public @interface EnableAutoConfiguration {
    String ENABLED_OVERRIDE_PROPERTY = "spring.boot.enableautoconfiguration";
    Class<?>[] exclude() default {};
    String[] excludeName() default {};
}

The annotation can be used to disable specific auto‑configurations via exclude or excludeName. Example:

// Exclude DataSourceAutoConfiguration via @SpringBootApplication
@SpringBootApplication(exclude = DataSourceAutoConfiguration.class)
public class SpringLearnApplication {}

or

// Exclude via @EnableAutoConfiguration directly
@Configuration
@EnableAutoConfiguration(exclude = DataSourceAutoConfiguration.class)
public class DemoConfiguration {}

Packages containing classes annotated with @EnableAutoConfiguration are also used as the base for entity scanning.

5. AutoConfigurationImportSelector

The AutoConfigurationImportSelector is imported by @EnableAutoConfiguration. Its selectImports method performs the bulk of the auto‑configuration logic, reading spring.factories, evaluating conditions, and returning the list of configuration classes to import.

6. Summary

The article provides a source‑level walkthrough of Spring Boot’s auto‑configuration mechanism, covering the role of starters, spring.factories, key annotations, and the import selector that ties everything together, enabling developers to understand and control the automatic bean registration process.