JDK-6447751 : Bean Customizer should be detectable by reflection name alone
- Type: Enhancement
- Component: client-libs
- Sub-Component: java.beans
- Affected Version: 6
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: windows_xp
- CPU: x86
- Submitted: 2006-07-11
- 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.
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 b121Fixed  |
Related Reports
|
Relates :
|
Description
A DESCRIPTION OF THE REQUEST : At the moment, PropertyEditors can be defined either by placing them in a BeanInfo or by naming the editor using the naming convention of appending 'Editor' to the property's class name. Unfortunately, the only way to declare a customizer is by inclusing it in a BeanInfo. It would be useful if customizers could also be specified by using the naming convention of appending Customizer to the name of the bean's class. JUSTIFICATION : BeanInfos are hard to maintain, and cause hard to find bugs when they are out of date.
Comments
|