Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NoSuchBeanDefinitionException message shows internal array class names [SPR-14595] #19164

Closed
spring-projects-issues opened this issue Aug 17, 2016 · 0 comments
Assignees
Labels
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Aug 17, 2016

Juergen Hoeller opened SPR-14595 and commented

Since 4.3's revision of the collection/array matching algorithm, a NoSuchBeanDefinitionException may get thrown with a undesirable reference to internal array class names instead of a proper ClassUtils.getQualifiedName representation.

Also, the primary type may get mentioned twice in the exception message which we should streamline towards a simpler message.


Affects: 4.3.2, 5.0 M1

Issue Links:

  • #12570 Allow for normal bean wiring semantics for types assignable to Map
  • #16794 @Autowired does not work for target bean of type Collection

Referenced from: commits 022b013, 7b11fa1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants