-
Bug
-
Resolution: Fixed
-
P5
-
1.3.0
-
None
-
rc1
-
generic
-
generic
The serialization specification presents specific signatures required for
class-defined custom serialization methods (e.g., writeReplace, readResolve,
writeObject, readObject). Currently, serialization will use a class-defined
custom serialization method so long as its access flags and parameter types
match those outlined in the specification. However, the serialization runtime
does not check the return type or thrown exception types to verify that they
are as expected.
class-defined custom serialization methods (e.g., writeReplace, readResolve,
writeObject, readObject). Currently, serialization will use a class-defined
custom serialization method so long as its access flags and parameter types
match those outlined in the specification. However, the serialization runtime
does not check the return type or thrown exception types to verify that they
are as expected.