未显式使用@Import注解，Spring自动装配仍生效的原因探究

Hey there! Let's unpack this—this is a super common point of confusion with Spring's configuration system, so you’re not alone in wondering about it. The short answer is: Spring is automatically detecting and registering your MySpringBeanConfig class (and its @Bean method) without you needing to explicitly @Import it.

Here’s the breakdown of how this happens:

1. Component Scanning is Doing the Heavy Lifting #

If you’re using Spring Boot (the standard for most modern Spring apps), your main application class is almost certainly annotated with @SpringBootApplication. This annotation includes @ComponentScan under the hood, which tells Spring to scan all packages under the package of your main class for components that should be added to the application context.

Your MySpringBeanConfig is marked with @Configuration, which Spring treats as a special type of component. As long as it lives in a package covered by @ComponentScan (e.g., your main class is in com.pkg.test and your config is in com.pkg.test.configuration), Spring will find it automatically. It will then execute the @Bean method and register that bean in the context—ready to be @Autowired anywhere you need it.

Even if you’re not using Spring Boot, if you’ve added @ComponentScan to any of your configuration classes (or set up component scanning via XML), the same logic applies: @Configuration classes in scanned packages get picked up automatically.

2. A Quick Fix for Your Code Snippet #

Side note: I noticed your @Bean method returns void—that’s a mistake! @Bean methods should return the actual type of the bean you want to register. For example:

@Bean
public MyBean constructMyBean() {
    return new MyBean();
}

Otherwise, Spring won’t register a bean from that method (since there’s no object to add to the context). I assume that’s just a typo in your snippet, but it’s worth double-checking!

What If You Wanted to Prevent This Automatic Registration? #

If you ever need to stop Spring from automatically detecting a configuration class, you have a few options:

• Move the config class to a package that’s outside the @ComponentScan scope
• Use @ComponentScan(excludeFilters = @Filter(type = FilterType.ANNOTATION, classes = Configuration.class)) to exclude all @Configuration classes from scanning, then explicitly @Import only the ones you want
• Mark the config class with @Conditional to control exactly when it gets registered

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