JDK-4222827 : RFE: Support getAsText and setAsText in all default editors
- Type: Enhancement
- Component: client-libs
- Sub-Component: java.beans
- Affected Version: 1.2.0
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 1999-03-23
- Updated: 2010-07-09
- 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.
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 | Other |
|---|---|
7 b10Fixed  |
OpenJDK6Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
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) ======================================================================
Comments
|