Currently the XSD->Java source generation can produce JavaBeans with bound properties.  These JavaBeans are serializable.  Due to the design of the generated code, PropertyChangeListeners added to the JavaBeans also get serialized.  In our case the serialization of these PropertyChangeListeners is generally not desirable, and actually prevents the use of serialization. 
 
I propose a change to the generated JavaBeans where the listeners are transient such that they are not included in the serialization/deserialization process (see http://jira.codehaus.org/browse/CASTOR-1152 for the patch).
 
Is this approach applicable to your project(s)?  Is there a case for including PropertyChangeListeners in serialization?  Is there a need for an option to enable/disable this feature when generating the JavaBeans, or is it valid to have the listeners always be transient?
 
I'm looking for feedback on this issue and hoping that someone on the committers list takes interest.
 
Thanks,

David

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.9/62 - Release Date: 8/2/2005

Reply via email to