JDK-6425896 : JSR 269: More fully specify behavior of TypeMirror.asElement
  • Type: Bug
  • Component: core-libs
  • Sub-Component: javax.lang.model
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-05-15
  • Updated: 2010-04-02
  • Resolved: 2006-07-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b91Fixed
Related Reports
Relates :  
Description
From notes on ealier versions of the specification:

There is a clear and natural association between many types and their corresponding elements. For example, the type declaration for C<T extends I> defines a family of declared types, and its type parameter <T extends I> defines the type variable named T. For other types, though, it is less clear what this method will return. This must be more fully specified. For instance, what element is returned for a primitive type, an array, an intersection type that forms the bound of a type variable, or a type variable implicitly defined by the capture conversion of a wildcard?

Comments
EVALUATION Proposed solution: Move asElement from TypeMirror down to more specific and appropriate subinterfaces. Add convenience method Types.asElement(TypeMirror).
23-06-2006

EVALUATION Should be fixed.
15-05-2006