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

[spring-projects-issues]

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:

• Allow for normal bean wiring semantics for types assignable to Map [SPR-7915] #12570 Allow for normal bean wiring semantics for types assignable to Map
• @Autowired does not work for target bean of type Collection [SPR-12180] #16794 @Autowired does not work for target bean of type Collection

Referenced from: commits 022b013, 7b11fa1