Improve error message when bean initialization fails [SPR-9891]

[spring-projects-issues]

Piotr Findeisen opened SPR-9891 and commented

When bean initialization fails due to whatever reason

• bean in depends-on is not defined
• circular depends-on Improve failure mode when depends-on cycles exist [SPR-7966] #12621
• and, in fact, anything else

exception raised should mention bean name in it's message to allow faster problem diagnosis

---

Affects: 3.1.2, 3.2 M2

1 votes, 2 watchers

[spring-projects-issues]

Piotr Findeisen commented

Rationale

When working on a bigger project, you often built application context using only a subset of XML files that exist (various application profiles, modules, test vs run-time configuration, mocks, etc.). When an exception is raised saying "No bean named 'XXX' is defined", it's not at all obvious where the problem lies.

Proposed solution

Wrap AbstractBeanFactory.doGetBean in a try-catch section that wraps exceptions in RuntimeException("Failed to get bean '<name>'")

[spring-projects-issues]

Sébastien Deleuze commented

Juergen Hoeller I would be tempted to resolve this old issue as works as designed, but could you please have a quick look to evaluate if there is easy room for improvement or if you think our current error messages are fine?

[spring-projects-issues]

Bulk closing outdated, unresolved issues. Please, reopen if still relevant.