While working on OJB-105 on the 1.0 branch I have come across some serialization issues with objects using OJB CollectionProxyDefaultImpl.
If an object with a reference of type CollectionProxyDefaultImpl (ie list proxy) is serialized and deserialized with JRE:s with different serialVersionUID algorithms the object won't load although the OJB class has not changed. Specifically this occured between Sun JRE 1.4.2_11 and 1.5.0_06. An explicit serialVersionUID field in OJB's CollectionProxyDefaultImpl prevents this: private static final long serialVersionUID = -9221388147166951006L; There are serveral classes in OJB that implements java.io.Serializable but do not define explicit serialVersionUID fields. Any objections if I would go ahead and check generated UID:s in? Any side-effects with that (other than the JRE i use using generation beeing normative)? Regards, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
