Odd behaviour with null bean instance when an alternative autowire candidate is available [SPR-16960] #21498
Closed as not planned
Description
Dave Syer opened SPR-16960 and commented
Since Spring 5.0 a @Bean can return null and the effect is to leave the bean definition in the registry, but make the value not autowirable. However, if there is another bean of the same type that is not null, it does not become autowirable. Probably it should? The exception from Spring doesn't mention the existence of either bean (the null or the not null one):
norg.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'java.lang.String' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)} at org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoMatchingBeanFound(DefaultListableBeanFactory.java:1509)
...
Affects: 5.0.7
Reference URL: spring-projects/spring-boot#13531
Issue Links:
- Null bean value exception message confusing [SPR-16961] #21499 Null bean value exception message confusing