|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I've created a test case with @Produces <T> Foo<T> produceFoo(InjectionPoint ip) and injection point @Inject Foo<List<?>> wildcardListFoo. The test passes without a problem.
Looks like the problem is in org.jboss.forge.furnace.container.cdi.impl.ContainerServiceExtension. It is creating a custom bean that has UIInput<FileResource<?>> among its bean types. A parameterized type with wildcards is not a legal bean type (http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#legal_bean_types). Weld should probably throw a definition exception if an extension tries to add a bean with an invalid bean type (I've filed WELD-1488)