[cdi-dev] [JBoss JIRA] (CDI-391) Type variable always has an upper bound

Jozef Hartinger created CDI-391: ----------------------------------- Summary: Type variable always has an upper bound Key: CDI-391 URL: https://issues.jboss.org/browse/CDI-391 Project: CDI Specification Issues Issue Type: Bug Components: Resolution Affects Versions: 1.1.FD Reporter: Jozef Hartinger The specification says: {quote} the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is assignable from the upper bound, if any, of the type variable, or {quote} or {quote} the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is assignable to the upper bound, if any, of the type variable, or {quote} depending on the version of the specification. These *if any* constructs are redundant since JLS defines that every type variable has an upper bound. Even if one is not explicitly declared, java.lang.Object is assumed as the upper bound. This fits the CDI rules well. http://docs.oracle.com/javase/specs/jls/se7/html/jls-4.html#jls-4.4 -- 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