Open mikehearn opened 3 months ago
The ExternalizableSerializer
has not been touched in a very long time. I'm guessing that not many people are using it. What use case do you have that prevents you from using FieldSerializer
or KryoSerializable
?
An object that wants to define its own serialization format independent of Kryo so it can ensure backwards compatibility as it evolves over time.
Describe the bug
If an object implements
Externalizable
and is registered with theExternalizableSerializer
, there is no way for it to callkryo.reference()
on itself and theExternalizableSerializer
doesn't do this either. As a consequence, if theExternalizable
attempts to read a reference to itself, it will getnull
and deserialize incorrectly.To Reproduce
Provide a minimal reproducible example of the problem, ideally in the form of a runnable test-case.
Environment:
Kryo 5.6.0