Name: ca25432 Date: 12/14/2001
Improve swing beans property editors, customizer only allows serialized bean
output. Request way to store customizations and data set in the object and allow snapshots of Swing beans, ie if double buffering is enabled
Also beaninfo data missing on Mac platform.
Provide XML based beaninfo document
=====================================================================
We will not be providing an XML Based BeanInfo document due to lack of resources. Instead, a JSR may be filed by IBM to drive this forward.
Much of the planning surrounding this feature is contained in the following document:
http://cerebus.sfbay/beans/tiger/propeditors.html
The document describes related improvements to PropertyEditors that have been filed under separate bugs. The only items not covered under separate RFEs and Bug which are applicable to the scope of this work are:
Clarification of the JavaBeans Specification
--------------------------------------------
The specification should be ammended to clearly specify which property editors will be provided by J2SE.
The getJavaInitializationString() should return a valid expression that uses a fully qualified class name. This has been an ongoing concern with the tool vendors.
All changes in PropertyEditors should be accompanied by PropertyChangeEvents.
De-emphasis PropertyEditors/JavaBeans from its GUI roots
--------------------------------------------------------
JavaBeans is the component model for Java but it still has a lot of remnants left over from it's GUI/AWT lineage. JavaBeans patterns are used in EJBs and can be directly referenced within jsps.
There is still a lot of kruft in the PropertyEditor interface left over from the BeanBox specific implemenation. These methods include:
* Component getCustomEditor() - Should return an Object. Check cast for Component for GUI builder.
* String[] getTags() - Poor context free version of enumeration. Forces hardcoding and inflexibility.
* boolean isPaintable()
* void paintValue(Graphics, Rectangle) - PropertyEditors shouldn't paint values. The custom editor should do this.
###@###.### 2002-12-03