Detector to find instances where code is attempting to
write an object out via an implemention of DataOutput,
but the object is not guaranteed to be Serializable.
This could be a false positive if the field is defined
as a non-serializable superclass but only Serializable
subclasses are actually ever stored in the field (i.e.
field is Collection, LinkedList is actually placed in
The only other (rarer) way this can be a false positive
is if the DataOutput is a subclass of
ObjectOutputStream which has called
enableReplaceObject(true) where the stream can define
serializable replacement objects for non-serializable
Log in to post a comment.