I don't understand why you don't intend to use BeanInfo instead of creating your own class descriptor (TypeDesc). I know that PropertyDescriptor doesn't contain all the informations required, but is it impossible to could extend it, or to use it by default, or something like that ...
Cédric -----Message d'origine----- De : R J Scheuerle Jr [mailto:[EMAIL PROTECTED]] Envoyé : samedi 20 avril 2002 00:09 À : [EMAIL PROTECTED] Objet : Bean Field Serialization/Deserialization There has been some discussion and bugs related to the serialization and deserialization of beans that do not have getter/setters but instead have public fields. I am working on the following change. Changes to utils.BeanPropertyDescriptor: * Add constructor to set BPD with a java.lang.reflect.Field. So now a BPD can be constructed for a Field or it can be constructed with a read/write Method pair. * Get rid of the getReadMethod/getWriteMethod methods. * Instead have set/get methods which will use the methods if available or use the field. * Have isReadable, isWriteable, isIndexed methods to query the BPD. Changes to utils.BeanUtils * Add the BPD's for public fields that do not have getters/setters. Changes to encoding/ser/BeanPropertyTarget * Change the getWriteMethod calls to use the new BPD.set calls...simplifies this code. Changes to encoding/ser/BeanSerializer & BeanDeserializer * Similar changes to remove getWriteMethod and getReadMethod calls and use the set/get and other query methods. This also simplifies the code. Any comments ? Rich Scheuerle XML & Web Services Development 512-838-5115 (IBM TL 678-5115)
