JDK-5020908 : Class-valued annotation elements not correctly represented in class file
  • Type: Bug
  • Component: specification
  • Sub-Component: language
  • Affected Version: 5.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS:
    generic,solaris_8,solaris_9,windows_xp generic,solaris_8,solaris_9,windows_xp
  • CPU: generic,x86,sparc
  • Submitted: 2004-03-26
  • Updated: 2021-04-20
  • Resolved: 2004-07-16
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.
Other
5.0 rcFixed
Related Reports
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Description

Name: ss24420			Date: 03/25/2004


This is really a JSR 175 spec bug.

Consider this annotation type:

    @interface A {
	Class value();
    }

and the annotation:

    @A(boolean.class)

The element value boolean.class is supposed to be represented in a
class file's constant_pool table using a CONSTANT_Class_info structure.
However, boolean isn't a class or interface, so it cannot be
represented by a CONSTANT_Class_info structure as currently spec'ed.

======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: tiger-rc INTEGRATED IN: tiger-rc
17-07-2004

EVALUATION The spec has been fixed to allow this information to be represented. ###@###.### 2004-07-15
15-07-2004