Re: Bug when serializing/deserializing objects

2019-02-28 Thread Lon Varscsak
Thanks for the quick fix! On Thu, Feb 28, 2019 at 4:26 AM Nikita Timofeev wrote: > Hi Lon, > > Thanks for example. This turned out to be a bug introduced in 4.1. > Old Map based CayenneDataObject incorrectly serialized/deserialized > HashMap with it's values. And that explains why you saw those

Re: Bug when serializing/deserializing objects

2019-02-28 Thread Nikita Timofeev
Hi Lon, Thanks for example. This turned out to be a bug introduced in 4.1. Old Map based CayenneDataObject incorrectly serialized/deserialized HashMap with it's values. And that explains why you saw those values in your other case. I've pushed fix for this to 4.1 branch and tested it with your

Re: Bug when serializing/deserializing objects

2019-02-27 Thread Lon Varscsak
Also wondering, would this be a more appropriate post for the "dev" list is or the "user" list appropriate/acceptable? -Lon On Wed, Feb 27, 2019 at 2:02 PM Andrus Adamchik wrote: > Hi Lon, > > We'll need to review this. All this used to worked before. > > Andrus > > > On Feb 26, 2019, at 1:00

Re: Bug when serializing/deserializing objects

2019-02-27 Thread Andrus Adamchik
Hi Lon, We'll need to review this. All this used to worked before. Andrus > On Feb 26, 2019, at 1:00 PM, Lon Varscsak wrote: > > I always forget this part, I'm working off of 4.1.M3-SNAPSHOT > > On Tue, Feb 26, 2019 at 10:54 AM Lon Varscsak > wrote: > >> Hey all, >> >> A few weeks ago I

Re: Bug when serializing/deserializing objects

2019-02-26 Thread Lon Varscsak
I always forget this part, I'm working off of 4.1.M3-SNAPSHOT On Tue, Feb 26, 2019 at 10:54 AM Lon Varscsak wrote: > Hey all, > > A few weeks ago I posted an email about a bug when serializing, and I > never really looked much more in to it. However, I've now encountered a > different issue if