When @DependsOn throws a NoSuchBeanDefinitionException it should include the dependent bean for clarity [SPR-16628]

[spring-projects-issues]

Kyle Anderson opened SPR-16628 and commented

When a bean annotated with @DependsOn references a bean name that doesn't exist, a NoSuchBeanDefinitionException is thrown.

Example:

org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'myMissingBean' available

I think this exception can be improved to contain information pertaining to the bean that was annotated with @DependsOn.

Example:

org.springframework.beans.factory.NoSuchBeanDefinitionException: 'com.example.MyBean' depends on a bean named 'myMissingBean' but it wasn't available

This would add a little extra clarity and traceability.

---

Affects: 4.3.14, 5.0.4

Reference URL: #1751

Backported to: 4.3.15

[spring-projects-issues]

Juergen Hoeller commented

Good point! We're wrapping such a depends-on NoSuchBeanDefinitionException in a BeanCreationException for the dependent bean now, like we do for circular dependencies and also for injected dependencies already.