Description
I observed a strange behavior on ignite-1.7. If I have an externalizable class inside of a serializable class and BinaryMarshaller is used, the externalizable class gets registered twice with different typeIds.
Looks like this happens because in BinaryWriterExImpl#marshal0 we first call ctx.descriptorForClass(cls, false) which will calculate and register type with one typeId. Then we figure out that the class is externalizable and switch to optimized marshaller (U.marshal(ctx.optimizedMarsh(), obj)) which will register another type ID.
Need to check if this is still reproducible in 2.1-2.2 as it may be a performance issue.
Attachments
Issue Links
- relates to
-
IGNITE-2894 Binary object inside of Externalizable still serialized with OptimizedMarshaller
- Open