spring boot实战(第十三篇)自动配置原理分析
前言
spring Boot中引入了自动配置,让开发者利用起来更加的简便、快捷,本篇讲利用RabbitMQ的自动配置为例讲分析下Spring Boot中的自动配置原理。
在上一篇末尾讲述了Spring Boot 默认情况下会为ConnectionFactory、RabbitTemplate等bean,在前面的文章中也讲到嵌入的Tomcat默认配置为8080端口
这些都属于Spring Boot自动配置的范畴,当然其自动配置相当多。
EnableAutoConfiguration注解
在创建Application时我们使用了SpringBootApplication注解,在spring boot实战(第九篇)Application创建源码分析中曾有所分析,再来看下其定义:
- @Target(ElementType.TYPE)
- @Retention(RetentionPolicy.RUNTIME)
- @Documented
- @Inherited
- @Configuration
- @EnableAutoConfiguration
- @ComponentScan
- public @interface SpringBootApplication {
- Class<?>[] exclude() default {};
- }
该注解上存在元注解@EnableAutoConfiguration,这就是Spring Boot自动配置实现的核心入口;其定义为:
- @Target(ElementType.TYPE)
- @Retention(RetentionPolicy.RUNTIME)
- @Documented
- @Inherited
- @Import({ EnableAutoConfigurationImportSelector.class,
- AutoConfigurationPackages.Registrar.class })
- public @interface EnableAutoConfiguration {
- /**
- * Exclude specific auto-configuration classes such that they will never be applied.
- * @return the classes to exclude
- */
- Class<?>[] exclude() default {};
- }
很显然能看出有一特殊的注解@Import,该注解在spring boot实战(第十篇)Spring boot Bean加载源码分析中有讲解到,加载bean时会解析Import注解,因此需要讲目光聚集在这段代码
- @Import({ EnableAutoConfigurationImportSelector.class,
- AutoConfigurationPackages.Registrar.class })
EnableAutoConfigurationImportSelector
来看EnableAutoConfigurationImportSelector类
- public String[] selectImports(AnnotationMetadata metadata) {
- try {
- AnnotationAttributes attributes = AnnotationAttributes.fromMap(metadata
- .getAnnotationAttributes(EnableAutoConfiguration.class.getName(),
- true));
- Assert.notNull(attributes, "No auto-configuration attributes found. Is "
- + metadata.getClassName()
- + " annotated with @EnableAutoConfiguration?");
- // Find all possible auto configuration classes, filtering duplicates
- List<String> factories = new ArrayList<String>(new LinkedHashSet<String>(
- SpringFactoriesLoader.loadFactoryNames(EnableAutoConfiguration.class,
- this.beanClassLoader)));
- // Remove those specifically disabled
- factories.removeAll(Arrays.asList(attributes.getStringArray("exclude")));
- // Sort
- factories = new AutoConfigurationSorter(this.resourceLoader)
- .getInPriorityOrder(factories);
- return factories.toArray(new String[factories.size()]);
- }
- catch (IOException ex) {
- throw new IllegalStateException(ex);
- }
- }
看如下代码,获取类路径下spring.factories下key为EnableAutoConfiguration全限定名对应值
- SpringFactoriesLoader.loadFactoryNames(EnableAutoConfiguration.class,
- this.beanClassLoader))
其结果为:
- # Auto Configure
- org.springframework.boot.autoconfigure.EnableAutoConfiguration=\
- org.springframework.boot.autoconfigure.aop.AopAutoConfiguration,\
- org.springframework.boot.autoconfigure.amqp.RabbitAutoConfiguration,\
- org.springframework.boot.autoconfigure.MessageSourceAutoConfiguration,\
- org.springframework.boot.autoconfigure.PropertyPlaceholderAutoConfiguration,\
- org.springframework.boot.autoconfigure.batch.BatchAutoConfiguration,\
- org.springframework.boot.autoconfigure.cloud.CloudAutoConfiguration,\
- org.springframework.boot.autoconfigure.dao.PersistenceExceptionTranslationAutoConfiguration,\
- org.springframework.boot.autoconfigure.data.elasticsearch.ElasticsearchRepositoriesAutoConfiguration,\
- org.springframework.boot.autoconfigure.data.jpa.JpaRepositoriesAutoConfiguration,\
- org.springframework.boot.autoconfigure.data.mongo.MongoRepositoriesAutoConfiguration,\
- org.springframework.boot.autoconfigure.data.solr.SolrRepositoriesAutoConfiguration,\
- org.springframework.boot.autoconfigure.data.rest.RepositoryRestMvcAutoConfiguration,\
- org.springframework.boot.autoconfigure.data.web.SpringDataWebAutoConfiguration,\
- org.springframework.boot.autoconfigure.freemarker.FreeMarkerAutoConfiguration,\
- org.springframework.boot.autoconfigure.gson.GsonAutoConfiguration,\
- org.springframework.boot.autoconfigure.hateoas.HypermediaAutoConfiguration,\
- org.springframework.boot.autoconfigure.integration.IntegrationAutoConfiguration,\
- org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration,\
- org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration,\
- org.springframework.boot.autoconfigure.jdbc.JndiDataSourceAutoConfiguration,\
- org.springframework.boot.autoconfigure.jdbc.XADataSourceAutoConfiguration,\
- org.springframework.boot.autoconfigure.jdbc.DataSourceTransactionManagerAutoConfiguration,\
- org.springframework.boot.autoconfigure.jms.JmsAutoConfiguration,\
- org.springframework.boot.autoconfigure.jmx.JmxAutoConfiguration,\
- org.springframework.boot.autoconfigure.jms.JndiConnectionFactoryAutoConfiguration,\
- org.springframework.boot.autoconfigure.jms.activemq.ActiveMQAutoConfiguration,\
- org.springframework.boot.autoconfigure.jms.hornetq.HornetQAutoConfiguration,\
- org.springframework.boot.autoconfigure.jta.JtaAutoConfiguration,\
- org.springframework.boot.autoconfigure.elasticsearch.ElasticsearchAutoConfiguration,\
- org.springframework.boot.autoconfigure.elasticsearch.ElasticsearchDataAutoConfiguration,\
- org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration,\
- org.springframework.boot.autoconfigure.groovy.template.GroovyTemplateAutoConfiguration,\
- org.springframework.boot.autoconfigure.jersey.JerseyAutoConfiguration,\
- org.springframework.boot.autoconfigure.liquibase.LiquibaseAutoConfiguration,\
- org.springframework.boot.autoconfigure.mail.MailSenderAutoConfiguration,\
- org.springframework.boot.autoconfigure.mobile.DeviceResolverAutoConfiguration,\
- org.springframework.boot.autoconfigure.mobile.DeviceDelegatingViewResolverAutoConfiguration,\
- org.springframework.boot.autoconfigure.mobile.SitePreferenceAutoConfiguration,\
- org.springframework.boot.autoconfigure.mongo.MongoAutoConfiguration,\
- org.springframework.boot.autoconfigure.mongo.MongoDataAutoConfiguration,\
- org.springframework.boot.autoconfigure.mustache.MustacheAutoConfiguration,\
- org.springframework.boot.autoconfigure.orm.jpa.HibernateJpaAutoConfiguration,\
- org.springframework.boot.autoconfigure.reactor.ReactorAutoConfiguration,\
- org.springframework.boot.autoconfigure.redis.RedisAutoConfiguration,\
- org.springframework.boot.autoconfigure.security.SecurityAutoConfiguration,\
- org.springframework.boot.autoconfigure.security.FallbackWebSecurityAutoConfiguration,\
- org.springframework.boot.autoconfigure.social.SocialWebAutoConfiguration,\
- org.springframework.boot.autoconfigure.social.FacebookAutoConfiguration,\
- org.springframework.boot.autoconfigure.social.LinkedInAutoConfiguration,\
- org.springframework.boot.autoconfigure.social.TwitterAutoConfiguration,\
- org.springframework.boot.autoconfigure.solr.SolrAutoConfiguration,\
- org.springframework.boot.autoconfigure.velocity.VelocityAutoConfiguration,\
- org.springframework.boot.autoconfigure.thymeleaf.ThymeleafAutoConfiguration,\
- org.springframework.boot.autoconfigure.web.DispatcherServletAutoConfiguration,\
- org.springframework.boot.autoconfigure.web.EmbeddedServletContainerAutoConfiguration,\
- org.springframework.boot.autoconfigure.web.ErrorMvcAutoConfiguration,\
- org.springframework.boot.autoconfigure.web.GzipFilterAutoConfiguration,\
- org.springframework.boot.autoconfigure.web.HttpEncodingAutoConfiguration,\
- org.springframework.boot.autoconfigure.web.HttpMessageConvertersAutoConfiguration,\
- org.springframework.boot.autoconfigure.web.MultipartAutoConfiguration,\
- org.springframework.boot.autoconfigure.web.ServerPropertiesAutoConfiguration,\
- org.springframework.boot.autoconfigure.web.WebMvcAutoConfiguration,\
- org.springframework.boot.autoconfigure.websocket.WebSocketAutoConfiguration
以上为Spring Boot中所有的自动配置相关类;在启动过程中会解析对应类配置信息,以RabbitMQ为例,则会去解析RabbitAutoConfiguration
RabbitAutoConfiguration
首先来看RabbitAutoConfiguration类上的注解:
- @Configuration
- @ConditionalOnClass({ RabbitTemplate.class, Channel.class })
- @EnableConfigurationProperties(RabbitProperties.class)
- @Import(RabbitAnnotationDrivenConfiguration.class)
- public class RabbitAutoConfiguration {
- @Configuration: 应该不需要解释
@ConditionalOnClass:表示存在对应的Class文件时才会去解析RabbitAutoConfiguration,否则直接跳过不解析,这也是为什么在不导入RabbitMQ依赖Jar时工程能正常启动的原因
@EnableConfigurationProperties:表示对@ConfigurationProperties的内嵌支持,默认会将对应Class这是为bean,例如这里值为RabbitProperties.class,其定义为:
- @ConfigurationProperties(prefix = "spring.rabbitmq")
- public class RabbitProperties {
- /**
- * RabbitMQ host.
- */
- private String host = "localhost";
- /**
- * RabbitMQ port.
- */
- private int port = 5672; .... //省略部分代码}
RabbitProperties提供对RabbitMQ的配置信息,其前缀为spring.rabbitmq,因此在上篇中配置的host、port等信息会配置到该类上,随后@EnableConfigurationProperties会将RabbitProperties注册为一个bean。
- @Import为导入配置,RabbitAnnotationDrivenConfiguration具体实现如下:
- @Configuration
- @ConditionalOnClass(EnableRabbit.class)
- class RabbitAnnotationDrivenConfiguration {
- @Autowired(required = false)
- private PlatformTransactionManager transactionManager;
- @Bean
- @ConditionalOnMissingBean(name = "rabbitListenerContainerFactory")
- public SimpleRabbitListenerContainerFactory rabbitListenerContainerFactory(
- ConnectionFactory connectionFactory) {
- SimpleRabbitListenerContainerFactory factory = new SimpleRabbitListenerContainerFactory();
- factory.setConnectionFactory(connectionFactory);
- if (this.transactionManager != null) {
- factory.setTransactionManager(this.transactionManager);
- }
- return factory;
- }
- @EnableRabbit
- @ConditionalOnMissingBean(name = RabbitListenerConfigUtils.RABBIT_LISTENER_ANNOTATION_PROCESSOR_BEAN_NAME)
- protected static class EnableRabbitConfiguration {
- }
- }
这里又涉及到一个重要的注解:@ConditionalOnMissingBean,其功能为如果存在指定name的bean,则该注解标注的bean不创建,
- @ConditionalOnMissingBean(name = "rabbitListenerContainerFactory")
表示的意思为:如果存在名称为rabbitListenerContainerFactory的bean,则该部分代码直接忽略,这是Spring Boot人性化体现之一,开发者申明的bean会放在第一位,实在是太懂礼貌了~~
- @Configuration
- @ConditionalOnMissingBean(ConnectionFactory.class)
- protected static class RabbitConnectionFactoryCreator {
- @Bean
- public ConnectionFactory rabbitConnectionFactory(RabbitProperties config) {
- CachingConnectionFactory factory = new CachingConnectionFactory();
- String addresses = config.getAddresses();
- factory.setAddresses(addresses);
- if (config.getHost() != null) {
- factory.setHost(config.getHost());
- factory.setPort(config.getPort());
- }
- if (config.getUsername() != null) {
- factory.setUsername(config.getUsername());
- }
- if (config.getPassword() != null) {
- factory.setPassword(config.getPassword());
- }
- if (config.getVirtualHost() != null) {
- factory.setVirtualHost(config.getVirtualHost());
- }
- return factory;
- }
- }
- @Bean
- @ConditionalOnMissingBean(RabbitTemplate.class)
- public RabbitTemplate rabbitTemplate() {
- return new RabbitTemplate(this.connectionFactory);
- }
创建了默认的RabbitTemplate;下面创建的RabbitMessagingTemplate实现对RabbitTemplate的包装。
spring boot实战(第十三篇)自动配置原理分析的更多相关文章
- Spring boot - 梳理 - 根本上说,Spring Boot项目只不过是一个普通的Spring项目,只是使用了Spring Boot的起步依赖和自动配置
根本上说,Spring Boot项目只不过是一个普通的Spring项目,只是使用了Spring Boot的起步依赖和自动配置
- Spring Boot实战系列(7)集成Consul配置中心
本篇主要介绍了 Spring Boot 如何与 Consul 进行集成,Consul 只是服务注册的一种实现,还有其它的例如 Zookeeper.Etcd 等,服务注册发现在微服务架构中扮演这一个重要 ...
- Spring Boot数据访问之数据源自动配置
Spring Boot提供自动配置的数据访问,首先体验下,Spring Boot使用2.5.5版本: 1)导入坐标: 2.5.25版本支持8.0.26mysql数据库驱动.spring-boot-st ...
- Spring Boot框架 - 数据访问 - JDBC&自动配置
一.新建Spring Boot 工程 特殊勾选数据库相关两个依赖 Mysql Driver — 数据库驱动 Spring Data JDBC 二.配置文件application.properties ...
- (转)spring boot实战(第三篇)事件监听源码分析
原文:http://blog.csdn.net/liaokailin/article/details/48194777 监听源码分析 首先是我们自定义的main方法: package com.lkl. ...
- (转)spring boot实战(第六篇)加载application资源文件源码分析
原文:http://blog.csdn.net/liaokailin/article/details/48878447
- spring boot实战(第十二篇)整合RabbitMQ
前言 最近几篇文章将围绕消息中间件RabbitMQ展开,对于RabbitMQ基本概念这里不阐述,主要讲解RabbitMQ的基本用法.Java客户端API介绍.spring Boot与RabbitMQ整 ...
- Spring Boot自动配置原理与实践(一)
前言 Spring Boot众所周知是为了简化Spring的配置,省去XML的复杂化配置(虽然Spring官方推荐也使用Java配置)采用Java+Annotation方式配置.如下几个问题是我刚开始 ...
- Spring Boot的自动配置原理及启动流程源码分析
概述 Spring Boot 应用目前应该是 Java 中用得最多的框架了吧.其中 Spring Boot 最具特点之一就是自动配置,基于Spring Boot 的自动配置,我们可以很快集成某个模块, ...
随机推荐
- “耐撕”团队第一次讨论——“抢答器”需求分析
团队名称:"耐撕" 团队成员:齐嘉亮.刘伟硕.濮成林.郑蕊 项目名称:"抢答器"(有待改善) 第一次讨论 时间:20160316 地点:软件所 人员:全体 内容 ...
- “耐撕”团队 2016.3.25 站立会议
成员: Z 郑蕊 * 组长 (博客:http://www.cnblogs.com/zhengrui0452/), P 濮成林(博客:http://www.cnblogs.com/charliePU/) ...
- java核心数据结构总结
JDK提供了一组主要的数据结构的实现,如List.Set.Map等常用结构,这些结构都继承自java.util.collection接口. List接口 List有三种不同的实现,ArrayList和 ...
- selenium常见的疑问和问题
.确认(verifation)和断言(assert)有什么区别? 确认:当测试中的一个用例存在错误时,系统将会继续运行这些测试 断言:当测试中的一个用例存在错误时,系统将会退出当前用例 总而言之 ...
- 以一个权限系统来告别WebForm —开篇
前言: 当今是互联网的时代,我们己经阻止不了它的发展了,只有跟上脚步,才不会被抛弃,松散了这么久,该紧紧了. 背景: 我之所以说以一个权限应用系统来告别我的WebForm内部系统的生涯,是缘于我自 ...
- Tomcat Can't load AMD 64-bit .dll on a IA 32
Java.lang.UnsatisfiedLinkError: C:\apache\apache-tomcat-7.0.14\bin\tcnative-1.dll: Can't load AMD 64 ...
- Android——Canvas类的学习
转:http://blog.sina.com.cn/s/blog_61ef49250100qw9x.html 今晚瞎折腾,闲着没事画了个机器人——android,浪费了一个晚上的时间.画这丫还真不容易 ...
- hihocoder 1154 Spring Outing
传送门 #1154 : Spring Outing 时间限制:20000ms 单点时限:1000ms 内存限制:256MB 描述 You class are planning for a spring ...
- Jquery——思维导图
- 织梦DedeCms去掉栏目页面包屑导航最后的分隔符“>”
织梦DedeCms的面包屑导航调用标签{dede:field name=’position’ /},在栏目页里调用的面包屑导航,最后会出现分割符号“>”,如:主页 > DedeCms 模板 ...