Generic autowiring should support wiring of components with unresolved type variables [SPR-10993]

[spring-projects-issues]

Oliver Drotbohm opened SPR-10993 and commented

If an ApplicationContext contains BeanDefinition instances for a type MyComponent<T> and you try to wire it to an injection point that explictly refers to a type parameter (e.g. MyComponent<String>) you currently get a NoSuchBeanDefinitionException.

---

Affects: 4.0 RC1

Issue Links:

• Autowiring of types narrows with generics does not work [SPR-11004] #15632 Autowiring of types narrows with generics does not work
• Autowiring of generic types [SPR-9965] #14599 Autowiring of generic types

Referenced from: commits 0851766

[spring-projects-issues]

nebhale commented

Sorry for the crossed wires, but there's now a duplicate issue at #15632. It has a simple test-case attached, if you need it, otherwise go ahead and kill it.

[spring-projects-issues]

Juergen Hoeller commented

DefaultListableBeanFactory performs a fallback check for autowire candidates now, which GenericTypeAwareAutowireCandidateResolver implements to accept raw type matches if the target class has unresolvable type variables. Full generic matches are still preferred; the BeanFactory will only start looking for fallback matches if the first pass led to an empty result.