Thanks, Dmitry.
>>2-3. In your case, you have and java.time.Ser in one of the fields of your
>>POJO (or maybe inside of depended object), and it is Externalizable. In such
>>case BinaryMarshalelr falls back to OptimizedMarshaller with all the issues.
>>Try to remove it from your POJOs or make transient.
Given that I have this class:
class NewOrderRequest {
int securityId;
Instant createdTime;
}
Instant has a writeReplace method that returns java.time.Ser.
Is the whole 'NewOrderRequest' fall back to OptimizedMarshaller? Or only
'createdTime' fall back to OptimizedMarshaller.
-Calvin
-----Original Message-----
From: dkarachentsev [mailto:[email protected]]
Sent: Thursday, June 28, 2018 2:59 PM
To: [email protected]
Subject: RE: Best practice for class versioning: marshaller error
Hi Calvin,
1. Enlist I mean that if you want, for example, to get to see what fields
present in BinaryObject. In other words, if you want to work with
BinaryObject directly. For POJO serialization/deserialization this should
not be and issue at all.
2-3. In your case, you have and java.time.Ser in one of the fields of your
POJO (or maybe inside of depended object), and it is Externalizable. In such
case BinaryMarshalelr falls back to OptimizedMarshaller with all the issues.
Try to remove it from your POJOs or make transient.
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
The content of this communication is intended for the recipient and is subject
to CLSA Legal and Regulatory Notices.
These can be viewed at https://www.clsa.com/disclaimer.html or sent to you upon
request.
Please consider before printing. CLSA is ISO14001 certified and committed to
reducing its impact on the environment.
