public class CompatibleFieldSerializer<T>extends FieldSerializer<T>
There is additional overhead compared to
FieldSerializer. A header is output the first time an object of a given type is serialized. The header consists of an int for the number of fields, then a String for each field name. Also, to support skipping the bytes for a field that no longer exists, for each field value an int is written that is the length of the value in bytes.
Note that the field data is identified by name. The situation where a super class has a field with the same name as a subclass must be avoided.
|Constructor and Description|
|Modifier and Type||Method and Description|
Reads bytes and returns a new object of the specified concrete type.
This method can be called for different fields having the same type.
compare, copy, create, createCopy, getField, getFields, getGenericsScope, getKryo, getType, getUseAsmEnabled, getUseMemRegions, initializeCachedFields, rebuildCachedFields, removeField, setFieldsAsAccessible, setFieldsCanBeNull, setFixedFieldTypes, setGenerics, setIgnoreSyntheticFields, setUseAsm
getAcceptsNull, isImmutable, setAcceptsNull, setImmutable
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
Before Kryo can be used to read child objects,
Kryo.reference(Object) must be called with the parent object to ensure it can be referenced by the child objects. Any serializer that uses
Kryo to read a child object may need to be reentrant.
This method should not be called directly, instead this serializer can be passed to
Kryo read methods that accept a serialier.
Copyright © 2013. All Rights Reserved.