Feature: Print object graph when serialization fails about kryo HOT 2 CLOSED

From [email protected] on August 13, 2010 15:16:15

Currently TRACE logging gives you the most information about serialization. I am open to ways we can improve the logging or otherwise provide a mechanism to make it more clear how serialization will be performed.

What exactly do you propose? What are some of the use cases? What are some of the ways that serialization fails that are difficult to figure out?

We could write a utility that prints out the object graph, navigating the graph via reflection similar to FieldSerializer. However, this may not accurately represent how the graph will be serialized. Eg, FieldSerializer can be configured to skip fields, the graph may not be serialized with FieldSerializer and would be walked differently for serialization, etc.

Maybe there is something fancy that can be done with method interception?

from kryo.

From [email protected] on August 16, 2010 21:41:15

(No comment was entered for this change.)

Status: Duplicate
Mergedinto: 21

from kryo.