RE: Binary object inside Externalizable

2016-02-24 Thread Andrey Kornev
, the Throwable class) that use Serializable. My point is that no matter how much we all love quick fixes, when it comes to serialization, all cases must be properly supported. Regards Andrey > From: valentin.kuliche...@gmail.com > Date: Tue, 23 Feb 2016 20:50:14 -0800 > Subject: Re: Binary obje

Re: Binary object inside Externalizable

2016-02-24 Thread Dmitriy Setrakyan
I am always in favor of easy fixes :) On Tue, Feb 23, 2016 at 8:50 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Actually, adding Externalizable support to binary marshaller should not be > difficult, no? BinaryWriterExImpl already implements ObjectOutput, so we > just need

Re: Binary object inside Externalizable

2016-02-23 Thread Valentin Kulichenko
Actually, adding Externalizable support to binary marshaller should not be difficult, no? BinaryWriterExImpl already implements ObjectOutput, so we just need to pass to writeExternal (and the same for deserialization). To be honest, I don't understand why we use optimized marshaller here and

Re: Binary object inside Externalizable

2016-02-20 Thread Dmitriy Setrakyan
Andrey, you are absolutely right. I was suggesting a quick fix, which in my view, would fix most of the issues. In the long term, we should fix the binary serialization to work the way you are describing. D. On Sat, Feb 20, 2016 at 9:26 AM, Andrey Kornev wrote: > Val,