JDK-6498171 : PropertyEditor.getJavaInitializationString() generates illegal Java code for some property editors
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.beans
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2006-11-28
  • Updated: 2011-03-08
  • Resolved: 2011-03-08
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 7
7 b10Fixed
Related Reports
Relates :  
JDK-6582164 - JavaBeans tests should be open source
Relates :  
JDK-6538853 - Default FontEditor generates incorrect text representation
Description
Some property editors do not support null values:
ByteEditor, ColorEditor, FloatEditor, FontEditor, LongEditor, ShortEditor
BooleanEditor.getJavaInitializationString() throws NPE.
ByteEditor.getJavaInitializationString() returns "((byte)null)".
ShortEditor.getJavaInitializationString() returns "((short)null)".
LongEditor.getJavaInitializationString() returns "nullL".
FloatEditor.getJavaInitializationString() returns "nullF".
ColorEditor.getJavaInitializationString() returns "new java.awt.Color()"
FontEditor.getJavaInitializationString() throws NPE.
Comments
EVALUATION Implementation of PropertyEditor.getJavaInitializationString() for default editors should be rewritten.
28-11-2006