11.bean中的autowire-candidate属性又是干什么的?

autowire-candidate到底是干什么的?

上一篇文章primary可以解决什么问题?中遇到的问题我们再来回顾一下,当容器中某种类型的bean存在多个的时候,此时如果我们从容器中查找这种类型的bean的时候,会报下面这个异常:

 
  1. org.springframework.beans.factory.NoUniqueBeanDefinitionException

原因:当从容器中按照类型查找一个bean对象的时候,容器中却找到了多个匹配的bean,此时spring不知道如何选择了,处于懵逼状态,就会报这个异常。

这种异常主要出现在2种场景中:

场景1:

从容器容器中查找符合指定类型的bean,对应BeanFactory下面的方法:

 
  1. <T> T getBean(Class<T> requiredType) throws BeansException;

场景2:

自动注入方式设置为byType的时候,如下:

 
  1. package com.javacode2018.lesson001.demo8;
  2. public class SetterBean {
  3. public interface IService{} //@1
  4. public static class ServiceA implements IService{} //@2
  5. public static class ServiceB implements IService{} //@3
  6. private IService service;
  7. public void setService(IService service) {
  8. this.service = service;
  9. }
  10. }
 
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <beans xmlns="http://www.springframework.org/schema/beans"
  3. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  4. xsi:schemaLocation="http://www.springframework.org/schema/beans
  5. http://www.springframework.org/schema/beans/spring-beans-4.3.xsd">
  6. <bean id="serviceA" class="com.javacode2018.lesson001.demo8.SetterBean$ServiceA"/>
  7. <bean id="serviceB" class="com.javacode2018.lesson001.demo8.SetterBean$ServiceB"/>
  8. <bean id="setterBean" class="com.javacode2018.lesson001.demo8.SetterBean" autowire="byType" />
  9. </beans>

setterBean的autowire设置的是byType,即按setter方法的参数类型自动注入,SetterBean的setService的类型是IService,而IService类有2个实现类:ServiceA和ServiceB,而容器容器中刚好有这2个实现类的bean:serviceA和serviceB,所以上面代码会报错,不知道注入的时候选择那个对象注入。

我们可以通过primary属性来指定一个主要的bean,当从容器中查找的时候,如果有多个候选的bean符合查找的类型,此时容器将返回primary=”true”的bean对象。

spring还有一种方法也可以解决这个问题,可以设置某个bean是否在自动注入的时候是否为作为候选bean,通过bean元素的autowire-candidate属性类配置,如下:

 
  1. <bean id="serviceA" class="com.javacode2018.lesson001.demo8.SetterBean$ServiceA" autowire-candidate="false"/>

autowire-candidate:设置当前bean在被其他对象作为自动注入对象的时候,是否作为候选bean,默认值是true。

来举例说明一下,以上面的setter注入的案例先来说一下注入的过程:

容器在创建setterBean的时候,发现其autowire为byType,即按类型自动注入,此时会在SetterBean类中查找所有setter方法列表,其中就包含了setService方法,setService方法参数类型是IService,然后就会去容器中按照IService类型查找所有符合条件的bean列表,此时容器中会返回满足IService这种类型并且autowire-candidate=”true”的bean,刚才有说过bean元素的autowire-candidate的默认值是true,所以容器中符合条件的候选bean有2个:serviceA和serviceB,setService方法只需要一个满足条件的bean,此时会再去看这个列表中是否只有一个主要的bean(即bean元素的primary=“ture”的bean),而bean元素的primary默认值都是false,所以没有primary为true的bean,此时spring容器懵了,不知道选哪个了,此时就报错了,抛出NoUniqueBeanDefinitionException异常

从上面过程中可以看出将某个候选bean的primary置为true就可以解决问题了。

或者只保留一个bean的autowire-candidate为true,将其余的满足条件的bean的autowire-candidate置为false,此时也可以解决这个问题,下面我们使用autowire-candidate来解决上面问题看一下效果:

SetterBean.java

 
  1. package com.javacode2018.lesson001.demo9;
  2. public class SetterBean {
  3. public interface IService {} //@1
  4. public static class ServiceA implements IService {} //@2
  5. public static class ServiceB implements IService {} //@3
  6. private IService service;
  7. public void setService(IService service) {
  8. this.service = service;
  9. }
  10. @Override
  11. public String toString() {
  12. return "SetterBean{" +
  13. "service=" + service +
  14. '}';
  15. }
  16. }

autowireCandidateBean.xml

 
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <beans xmlns="http://www.springframework.org/schema/beans"
  3. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  4. xsi:schemaLocation="http://www.springframework.org/schema/beans
  5. http://www.springframework.org/schema/beans/spring-beans-4.3.xsd">
  6. <bean id="serviceA" class="com.javacode2018.lesson001.demo9.SetterBean$ServiceA" autowire-candidate="false"/>
  7. <bean id="serviceB" class="com.javacode2018.lesson001.demo9.SetterBean$ServiceB"/>
  8. <bean id="setterBean" class="com.javacode2018.lesson001.demo9.SetterBean" autowire="byType" />
  9. </beans>

上面我们将serviceA的autowire-candidate置为false了,serviceA在被其他bean自动按照类型注入的时候,将不再放入候选名单中

测试用例

 
  1. package com.javacode2018.lesson001.demo9;
  2. import com.javacode2018.lesson001.demo5.IocUtils;
  3. import com.javacode2018.lesson001.demo8.NormalBean;
  4. import com.javacode2018.lesson001.demo8.PrimaryBean;
  5. import org.junit.Test;
  6. import org.springframework.context.support.ClassPathXmlApplicationContext;
  7. import java.util.Arrays;
  8. import java.util.Map;
  9. /**
  10. * 公众号:路人甲Java,工作10年的前阿里P7分享Java、算法、数据库方面的技术干货!坚信用技术改变命运,让家人过上更体面的生活!
  11. * bean元素的autowire-candidate可以设置当前bean是否作为其他bean自动注入的候选bean
  12. */
  13. public class AutowireCandidateTest {
  14. @Test
  15. public void setterBean() {
  16. String beanXml = "classpath:/com/javacode2018/lesson001/demo9/autowireCandidateBean.xml";
  17. ClassPathXmlApplicationContext context = IocUtils.context(beanXml);
  18. System.out.println(context.getBean(SetterBean.class)); //@1
  19. SetterBean.IService service = context.getBean(SetterBean.IService.class); //@2
  20. System.out.println(service);
  21. }
  22. }

@1:查找容器中SetterBean类型的bean对象

@2:查找容器中SetterBean.IService接口类型的bean,实际上面容器中serviceA和serviceB都是这种类型的

下面我们运行一下,看看输出:

 
  1. SetterBean{service=com.javacode2018.lesson001.demo9.SetterBean$ServiceB@29176cc1}
  2. com.javacode2018.lesson001.demo9.SetterBean$ServiceB@29176cc1

注意一下输出,2行输出中都是ServiceB,因为serviceB的autowire-candidate是默认值true,自动注入的时候作为候选bean,而serviceA的autowire-candidate是false,自动注入的时候不作为候选bean,所以上面输出的都是serviceB。

autowire-candidates属性解析源码

beans元素是xml中定义bean的根元素,beans元素有个default-autowire-candidates属性,用于定义哪些bean可以作为候选者,default-autowire-candidates的值是个通配符如:

 
  1. default-autowire-candidates="*Service"

再来说一下bean元素的autowire-candidate属性,这个属性有3个可选值:

  • default:这个是默认值,autowire-candidate如果不设置,其值就是default
  • true:作为候选者
  • false:不作为候选者

spring中由beans元素的default-autowire-candidates和bean元素的autowire-candidate来决定最终bean元素autowire-candidate的值,我们来看一下bean元素autowire-candidates的解析源码:

 
  1. 源码位置:org.springframework.beans.factory.xml.BeanDefinitionParserDelegate#parseBeanDefinitionAttributes

主要代码如下:

 
  1. //获取bean元素的autowire-candidate元素,autowire-candidate如果不设置,其值就是default
  2. String autowireCandidate = ele.getAttribute(AUTOWIRE_CANDIDATE_ATTRIBUTE);
  3. //判断bean元素的autowire-candidate元素是否等于"default"或者是否等于""
  4. if (isDefaultValue(autowireCandidate)) {
  5. //获取beans元素default-autowire-candidates属性值
  6. String candidatePattern = this.defaults.getAutowireCandidates();
  7. //判断获取beans元素default-autowire-candidates属性值是否为空,default-autowire-candidates默认值就是null
  8. if (candidatePattern != null) {
  9. //判断bean的名称是否和default-autowire-candidates的值匹配,如果匹配就将bean的autowireCandidate置为true,否则置为false
  10. String[] patterns = StringUtils.commaDelimitedListToStringArray(candidatePattern);
  11. bd.setAutowireCandidate(PatternMatchUtils.simpleMatch(patterns, beanName));
  12. }
  13. }else {
  14. //判断bean的autowire-candidate的值是否等于"true"
  15. bd.setAutowireCandidate(TRUE_VALUE.equals(autowireCandidate));
  16. }

如果上面判断都没有进去,autowireCandidate属性默认值就是true,这个在下面定义的:

 
  1. org.springframework.beans.factory.support.AbstractBeanDefinition#autowireCandidate
  2. private boolean autowireCandidate = true;

所有的bean元素最后都会被解析为spring中的org.springframework.beans.factory.config.BeanDefinition对象,关于BeanDefinition以后我们会细说

问题

对上面的案例做个扩展,SetterBean类中加个方法:

 
  1. public void setService1(List<IService> service) {//@0
  2. System.out.println(service); //@1
  3. }

@0:需要注入一个IService的集合,判断一下@1输出的是容器中的serviceA,还是serviceB,还是2个都有呢?为什么?

案例源码

 
  1. 链接:https://pan.baidu.com/s/1p6rcfKOeWQIVkuhVybzZmQ
  2. 提取码:zr99
帮我看看这段日志,cassandra连接正常了吗?这个报错是因为什么? 2025-08-28 12:03:55.407 INFO 17536 --- [ main] c.t.n.d.b.BasicSpringBootApplication : Starting BasicSpringBootApplication on 18088172-BG with PID 17536 (E:\code\java\basic-spring-boot\target\classes started by admin in E:\code\java\basic-spring-boot) 2025-08-28 12:03:55.409 INFO 17536 --- [ main] c.t.n.d.b.BasicSpringBootApplication : No active profile set, falling back to default profiles: default 2025-08-28 12:03:55.824 INFO 17536 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode! 2025-08-28 12:03:55.825 INFO 17536 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data Reactive Cassandra repositories in DEFAULT mode. 2025-08-28 12:03:55.849 INFO 17536 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Reactive Cassandra - Could not safely identify store assignment for repository candidate interface com.tplink.nbu.demo.basicspringboot.repository.MysqlUserRepository. If you want this repository to be a Reactive Cassandra repository, consider annotating your entities with one of these annotations: org.springframework.data.cassandra.core.mapping.Table (preferred), or consider extending one of the following types with your repository: org.springframework.data.cassandra.repository.ReactiveCassandraRepository. 2025-08-28 12:03:55.849 INFO 17536 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 23ms. Found 0 Reactive Cassandra repository interfaces. 2025-08-28 12:03:55.851 INFO 17536 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode! 2025-08-28 12:03:55.851 INFO 17536 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data Cassandra repositories in DEFAULT mode. 2025-08-28 12:03:55.854 INFO 17536 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Cassandra - Could not safely identify store assignment for repository candidate interface com.tplink.nbu.demo.basicspringboot.repository.MysqlUserRepository. If you want this repository to be a Cassandra repository, consider annotating your entities with one of these annotations: org.springframework.data.cassandra.core.mapping.Table (preferred), or consider extending one of the following types with your repository: org.springframework.data.cassandra.repository.CassandraRepository. 2025-08-28 12:03:55.861 INFO 17536 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 10ms. Found 1 Cassandra repository interfaces. 2025-08-28 12:03:55.864 INFO 17536 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode! 2025-08-28 12:03:55.864 INFO 17536 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode. 2025-08-28 12:03:55.869 INFO 17536 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data JPA - Could not safely identify store assignment for repository candidate interface com.tplink.nbu.demo.basicspringboot.repository.CassandraUserRepository. If you want this repository to be a JPA repository, consider annotating your entities with one of these annotations: javax.persistence.Entity, javax.persistence.MappedSuperclass (preferred), or consider extending one of the following types with your repository: org.springframework.data.jpa.repository.JpaRepository. 2025-08-28 12:03:55.873 INFO 17536 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 7ms. Found 1 JPA repository interfaces. 2025-08-28 12:03:56.244 INFO 17536 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http) 2025-08-28 12:03:56.290 INFO 17536 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat] 2025-08-28 12:03:56.290 INFO 17536 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.34] 2025-08-28 12:03:56.415 INFO 17536 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext 2025-08-28 12:03:56.415 INFO 17536 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 991 ms 2025-08-28 12:03:56.555 INFO 17536 --- [ main] com.datastax.driver.core : DataStax Java driver 3.6.0 for Apache Cassandra 2025-08-28 12:03:56.557 INFO 17536 --- [ main] c.d.driver.core.GuavaCompatibility : Detected Guava >= 19 in the classpath, using modern compatibility layer 2025-08-28 12:03:56.636 INFO 17536 --- [ main] com.datastax.driver.core.Native : Could not load JNR C Library, native system calls through this library will not be available (set this logger level to DEBUG to see the full stack trace). 2025-08-28 12:03:56.637 INFO 17536 --- [ main] com.datastax.driver.core.ClockFactory : Using java.lang.System clock to generate timestamps. 2025-08-28 12:03:56.753 INFO 17536 --- [ main] com.datastax.driver.core.NettyUtil : Did not find Netty's native epoll transport in the classpath, defaulting to NIO. 2025-08-28 12:03:57.754 INFO 17536 --- [ main] c.d.d.c.p.DCAwareRoundRobinPolicy : Using data-center name 'datacenter1' for DCAwareRoundRobinPolicy (if this is incorrect, please provide the correct datacenter name with DCAwareRoundRobinPolicy constructor) 2025-08-28 12:03:57.755 INFO 17536 --- [ main] com.datastax.driver.core.Cluster : New Cassandra host /192.168.131.129:9042 added 2025-08-28 12:03:58.195 INFO 17536 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting... 2025-08-28 12:03:58.267 INFO 17536 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed. 2025-08-28 12:03:58.309 INFO 17536 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [ name: default ...] 2025-08-28 12:03:58.404 INFO 17536 --- [ main] org.hibernate.Version : HHH000412: Hibernate Core {5.3.17.Final} 2025-08-28 12:03:58.405 INFO 17536 --- [ main] org.hibernate.cfg.Environment : HHH000206: hibernate.properties not found 2025-08-28 12:03:58.577 INFO 17536 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.0.4.Final} 2025-08-28 12:03:58.707 INFO 17536 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect Hibernate: create table mysql_user (id bigint not null auto_increment, address varchar(255), email varchar(255) not null, password varchar(255) not null, username varchar(255) not null, valid bit, primary key (id)) engine=MyISAM Hibernate: alter table mysql_user drop index UK_4bc87y5bgn3lf60kknjot06g0 Hibernate: alter table mysql_user add constraint UK_4bc87y5bgn3lf60kknjot06g0 unique (email) 2025-08-28 12:03:59.316 INFO 17536 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default' 2025-08-28 12:03:59.386 WARN 17536 --- [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'DBOpController': Unsatisfied dependency expressed through field 'userService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'userServiceImpl': Unsatisfied dependency expressed through field 'userrepository'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.tplink.nbu.demo.basicspringboot.repository.UserRepository' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true), @org.springframework.beans.factory.annotation.Qualifier(value=mysqluserrepo)} 2025-08-28 12:03:59.386 INFO 17536 --- [ main] j.LocalContainerEntityManagerFactoryBean : Closing JPA EntityManagerFactory for persistence unit 'default' 2025-08-28 12:04:01.475 INFO 17536 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown initiated... 2025-08-28 12:04:01.481 INFO 17536 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown completed. 2025-08-28 12:04:01.482 INFO 17536 --- [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat] 2025-08-28 12:04:01.489 INFO 17536 --- [ main] ConditionEvaluationReportLoggingListener : Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled. 2025-08-28 12:04:01.613 ERROR 17536 --- [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPLICATION FAILED TO START *************************** Description: Field userrepository in com.tplink.nbu.demo.basicspringboot.service.UserServiceImpl required a bean of type 'com.tplink.nbu.demo.basicspringboot.repository.UserRepository' that could not be found. The injection point has the following annotations: - @org.springframework.beans.factory.annotation.Autowired(required=true) Action: Consider defining a bean of type 'com.tplink.nbu.demo.basicspringboot.repository.UserRepository' in your configuration.
08-29
从日志来看,**Cassandra连接本身是正常的**,但应用启动失败的原因是**Spring依赖注入问题**,而不是Cassandra连接问题。以下是关键点分析: --- ### **1. Cassandra连接成功迹象** - 日志中显示Cassandra驱动成功加载,并检测到主机: ``` 2025-08-28 12:03:57.755 INFO 17536 --- [main] com.datastax.driver.core.Cluster : New Cassandra host /192.168.131.129:9042 added ``` 这说明Cassandra服务已成功连接,且驱动检测到了节点(默认数据中心名`datacenter1`)。 --- ### **2. 应用启动失败的真正原因** 错误根源是 **Spring无法注入`UserRepository`的Bean**,具体表现为: ``` 2025-08-28 12:03:59.386 WARN 17536 --- [main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'DBOpController': Unsatisfied dependency expressed through field 'userService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'userServiceImpl': Unsatisfied dependency expressed through field 'userrepository'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.tplink.nbu.demo.basicspringboot.repository.UserRepository' available ``` #### **可能的原因** 1. **`UserRepository`接口未正确扩展Spring Data的Repository基类**(如`JpaRepository`或`CassandraRepository`)。 2. **包扫描未覆盖`UserRepository`所在的包**,导致Spring无法识别。 3. **注解冲突**: - 日志中显示同时配置了JPA和Cassandra的Repository,但实体类可能未正确标注`@Table`(Cassandra)或`@Entity`(JPA)。 - 例如:`MysqlUserRepository`被误认为Cassandra Repository(日志中有警告)。 --- ### **3. 解决方案** 1. **检查`UserRepository`接口定义**: - 确保它扩展了正确的基类(如`CassandraRepository`或`JpaRepository`)。 - 示例: ```java public interface UserRepository extends CassandraRepository<User, Long> {} ``` 2. **检查实体类注解**: - Cassandra实体需要`@Table`注解,JPA实体需要`@Entity`。 - 示例: ```java @Table("users") // Cassandra public class User { /* ... */ } ``` 3. **检查包扫描配置**: - 确保`@SpringBootApplication`或`@EnableCassandraRepositories`注解扫描到了`UserRepository`所在的包。 4. **排除多数据源冲突**: - 如果同时使用JPA和Cassandra,需通过`@Qualifier`明确指定注入的Repository。 --- ### **4. 其他日志中的无关警告** - `Could not load JNR C Library`:Cassandra驱动缺少本地库,不影响功能。 - `Did not find Netty's native epoll transport`:默认使用NIO,非致命错误。 ---
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值