-
Enhancement
-
Resolution: Fixed
-
P4
-
1.2.0
-
b10
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2157579 | OpenJDK6 | Sergey Malenkov | P3 | Resolved | Fixed | b03 |
Name: vi73552 Date: 03/22/99
Its important that the default editors support the getAsText and
setAsText methods. In my case, I'm using property editors to
convert string values from an applet's HTML page into actual
objects. Displaying a GUI object is inappropriate in this case.
The code works for all classes, except Font and Color because the
default editors for these classes don't implement the setAsText
method (it throws IllegalArgumentException for every input).
The Font and Color editors should accept strings in the same
form as their corresponding "decode" method. The getAsText method
will also need to be implemented.
(Review ID: 55589)
======================================================================
Its important that the default editors support the getAsText and
setAsText methods. In my case, I'm using property editors to
convert string values from an applet's HTML page into actual
objects. Displaying a GUI object is inappropriate in this case.
The code works for all classes, except Font and Color because the
default editors for these classes don't implement the setAsText
method (it throws IllegalArgumentException for every input).
The Font and Color editors should accept strings in the same
form as their corresponding "decode" method. The getAsText method
will also need to be implemented.
(Review ID: 55589)
======================================================================
- backported by
-
JDK-2157579 RFE: Support getAsText and setAsText in all default editors
-
- Resolved
-
- relates to
-
JDK-6538876 api/java_beans/PropertyEditorSupport/descriptions.html#EditorSupport problem with null value
-
- Closed
-
-
-
- Resolved
-
-
-
- Closed
-