Hello! It's not recommended to have class hierarchies with raw reading/writing. If you must, make sure to design your classes carefully so this isn't a problem.
The limitation is in place because raw reader resets position in stream. I think it could be removed with some effort, but I don't see why it would be worth the hassle. Regards, -- Ilya Kasnacheev чт, 3 окт. 2019 г. в 20:59, [email protected] <[email protected] >: > Hi Ilya, > > Thanks for your reply. I tried to program it around and I do not see > exception anymore, but still need to verify object is built correctly or > not. > > For complex or deep class hierarchy this seems a bit of hassle and not > maintainable. Could you please throw some light on why this limitation is > needed? and why it is not enforced for rawWriter? > > Thanks, > -Sam > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
