JDK-4763438 : Replace uses of @beaninfo with meta facility in core j2se
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: java.beans
  • Affected Version: 5.0,6,7,8,9
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-10-15
  • Updated: 2017-05-16
  • Resolved: 2015-10-07
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 9
9 b89Fixed
Related Reports
Blocks :  
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
At present, the @beaninfo tag is used some AWT and Swing code so that a custom doclet can automatically generate beaninfo classes.  The general meta facility planned for 1.5 may be able to replace @beaninfo for this purpose.  One advantage to the replacing @beaninfo with meta is that presumably the meta tag would be recoginized by the standard doclet used to generate the JavaDoc for the jdk (the beaninfo tag is not currently recognized).

Comments
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014

- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014

The basic idea of my fix is to avoid automatically generated classes to simplify the modularization (see 7179078). Actually, all BeanInfo are automatically generated at runtime, but several Swing classes have extended BeanInfo classes. These classes are generated at compile-time and then are packed into dt.jar. 1. Classes of the same package are in different jars. It complicates the modularization. 2. Javadoc provides the @beaninfo tags, which does not correspond to the BeanInfo, if dt.jar is not loaded. 3. Users have to create custom BeanInfo classes, which is not a trivial task (see 4058433). I want to solve these problems: 1. Additional BeanInfo classes will be replaced with annotations that will be used to generate BeanInfo on fly. 2. Generated BeanInfo will always correspond to these annotations. 3. Users will use this annotations for their Beans too.
07-04-2014

The webrev for this feature appears to be using core reflection of annotations rather than compile-time processing of annotations using annotation processors in javac. If the latter is of interest, please contact me for a design discussion.
04-04-2014

http://cr.openjdk.java.net/~malenkov/4763438.9.1/ The second version of the fix provides the javadoc for new annotations.
04-04-2014

We should fix this issue before the 7179078 bug.
25-03-2014

http://cr.openjdk.java.net/~malenkov/4763438.9.0/
25-03-2014

Attached GetPD.java file could be used to get information about all classes in java.awt and javax.swing packages: %JAVA_HOME%\bin\javac.exe GetPD.java %JAVA_HOME%\bin\java.exe GetPD > without.txt %JAVA_HOME%\bin\java.exe -cp .;%JAVA_HOME%\lib\dt.jar GetPD > with.txt diff -u2 without.txt with.txt > dt.diff Resulting dt.diff file is also attached. It shows what we should change.
21-11-2013

The beaninfo.txt file contains all usages of @beaninfo tag in JDK.
21-11-2013

EVALUATION Some new annotations for JavaBeans are developed for the JSR 273. We can use them after submitting this JSR.
31-08-2007

PUBLIC COMMENTS .
10-06-2004

EVALUATION This feature requires deliverables from JSR 175. ###@###.### 2002-10-21
21-10-2002