关于@SpringBootApplication注解,其内部主要是
@Target({ElementType.TYPE})
@Retention(RetentionPolicy.RUNTIME)
@Documented
@Inherited
@SpringBootConfiguration
@EnableAutoConfiguration
@ComponentScan(
excludeFilters = {@Filter(
type = FilterType.CUSTOM,
classes = {TypeExcludeFilter.class}
), @Filter(
type = FilterType.CUSTOM,
classes = {AutoConfigurationExcludeFilter.class}
)}
)
public @interface SpringBootApplication {
其中的@SpringBootConfiguration中含有@Configuration注解,后者表示这是一个配置类,所以@SpringBootConfiguration表示这是一个SpringBoot配置类
@ComponentScan表示扫描类,可以在里面配置扫描的包的路径,意义不大
@EnableAutoConfiguration注解,内部如下所示,可以看出主要是由@AutoConfigurationPackage @Import({AutoConfigurationImportSelector.class})俩个注解合成的
package org.springframework.boot.autoconfigure;
import java.lang.annotation.Documented;
import java.lang.annotation.ElementType;
import java.lang.annotation.Inherited;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
import org.springframework.context.annotation.Import;
@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 {};
}
点开@AutoConfigurationPackage注解,代码如下
//
// Source code recreated from a .class file by IntelliJ IDEA
// (powered by FernFlower decompiler)
//
package org.springframework.boot.autoconfigure;
import java.lang.annotation.Documented;
import java.lang.annotation.ElementType;
import java.lang.annotation.Inherited;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
import org.springframework.boot.autoconfigure.AutoConfigurationPackages.Registrar;
import org.springframework.context.annotation.Import;
@Target({ElementType.TYPE})
@Retention(RetentionPolicy.RUNTIME)
@Documented
@Inherited
@Import({Registrar.class})
public @interface AutoConfigurationPackage {
String[] basePackages() default {};
Class<?>[] basePackageClasses() default {};
}
继续点开里面的@Import({Registrar.class})中的Registrar,发现里面有一个registerBeanDefinitions方法,里面存在一个new AutoConfigurationPackages.PackageImports(metadata)).getPackageNames(),返回的值刚好是该主程序类所在的包的路径(com.llq),这也就解释了为什么@SpringBootApplication只能扫描和主程序类在同一包下的所有类,而不能扫描上层包下的类的原因
static class Registrar implements ImportBeanDefinitionRegistrar, DeterminableImports {
Registrar() {
}
public void registerBeanDefinitions(AnnotationMetadata metadata, BeanDefinitionRegistry registry) {
AutoConfigurationPackages.register(registry, (String[])(new AutoConfigurationPackages.PackageImports(metadata)).getPackageNames().toArray(new String[0]));
}
public Set<Object> determineImports(AnnotationMetadata metadata) {
return Collections.singleton(new AutoConfigurationPackages.PackageImports(metadata));
}
}
再次回到@EnableAutoConfiguration注解,关注其内部@Import({AutoConfigurationImportSelector.class})注解,点开AutoConfigurationImportSelector类,内部存在这个方法
protected AutoConfigurationImportSelector.AutoConfigurationEntry getAutoConfigurationEntry(AnnotationMetadata annotationMetadata) {
if (!this.isEnabled(annotationMetadata)) {
return EMPTY_ENTRY;
} else {
AnnotationAttributes attributes = this.getAttributes(annotationMetadata);
List<String> configurations = this.getCandidateConfigurations(annotationMetadata, attributes);
configurations = this.removeDuplicates(configurations);
Set<String> exclusions = this.getExclusions(annotationMetadata, attributes);
this.checkExcludedClasses(configurations, exclusions);
configurations.removeAll(exclusions);
configurations = this.getConfigurationClassFilter().filter(configurations);
this.fireAutoConfigurationImportEvents(configurations, exclusions);
return new AutoConfigurationImportSelector.AutoConfigurationEntry(configurations, exclusions);
}
}
在这里面自动装配127个场景的自动配置,因为存在@Conditional注解,所以其内部有很多配置无法生效
其内部还有些东西没怎么看懂,先放上网上的一小段总结
----------------------------------------------
总结:SpringBoot先加载所有的自动配置类,xxxxAutoConfiguration
每个自动配置类按照条件进行生效,默认都会绑定配置文件指定的值,xxxxProperties里面拿,其中xxxProperties和咱们自己的配置文件进行了绑定
生效的配置类会给容器中配置很多组件,反之不配置
只要容器中有这些组件,相当于这些功能就有了
定制化配置:1.用户直接自己@Bean替换底层的组件2.直接去自己的配置文件进行修改