JDK-8207816 : Align declaration of SerializedLambda.readResolve with serialization conventions
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang.invoke
  • Affected Version: 11
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-07-19
  • Updated: 2018-07-26
  • Resolved: 2018-07-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 12
12 b04Fixed
Related Reports
Relates :  
JDK-8202056 - Expand serial warning to check for bad overloads of serial-related methods and ineffectual fields
Relates :  
JDK-8207751 - Remove misleading serialVersionUID from JulienFields.Field
Relates :  
JDK-8208060 - Additional corrections of serial-related declarations
Relates :  
JDK-8203263 - Remove unnecessary throws clauses from serialization-related methods
Description
Per the serialization specification, the readResolve method is supposed to be declared as follows:

ANY-ACCESS-MODIFIER Object readResolve()
            throws ObjectStreamException;
https://docs.oracle.com/javase/10/docs/specs/serialization/input.html#the-readresolve-method

The SerializedLambda class instead declares readResolve to throw ReflectiveOperationException.