S
Shin
Hello,
When you are doing RMI or other tasks involving Serialization of Java
objects, I guess you can run into "NotSerializableException". However,
this exception can happen while the serialization code is tranversing
some complicated object graph, so my question is: is there a quick way
to determine which field in which class actually causes this
NotSerializableException?
The stack trace only points to which class is not serializable, and
which RMI call the marshalling process is servicing. (In other words,
only the "head" and "tail", but lacks the most relevant information for
debugging purpose).
Thanks,
-Shin
When you are doing RMI or other tasks involving Serialization of Java
objects, I guess you can run into "NotSerializableException". However,
this exception can happen while the serialization code is tranversing
some complicated object graph, so my question is: is there a quick way
to determine which field in which class actually causes this
NotSerializableException?
The stack trace only points to which class is not serializable, and
which RMI call the marshalling process is servicing. (In other words,
only the "head" and "tail", but lacks the most relevant information for
debugging purpose).
Thanks,
-Shin