JDK-8233091 : Backout JDK-8212117: Class.forName loads a class but not linked if class is not initialized
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang:class_loading
  • Affected Version: 14
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-10-28
  • Updated: 2019-11-13
  • Resolved: 2019-11-04
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 14
14 b22Fixed
Related Reports
CSR :  
JDK-8233260 - Class.forName should be able to load, but not link, a class
Duplicate :  
JDK-8231924 - Field::getGenericType triggers loading and linking that may fail with LinkageError
Relates :  
JDK-8181144 - JDI - VirtualMachine.allClasses() does not return loaded but uninitialized class
Relates :  
JDK-8233272 - The Class.forName specification should be updated to match the long-standing implementation with respect to class linking
Relates :  
JDK-8212117 - Class.forName may return a reference to a loaded but not linked Class
Relates :  
JDK-8227926 - add new JVM TI and JDI tests for classes loaded by Class::forName
Description
Given JDK-8231924 (and other reports), we should reconsider the behavior change make in JDK-8212117 such that Class.forName always performs class loading as well as linking.
Comments
URL: https://hg.openjdk.java.net/jdk/jdk/rev/d67ebc838ab8 User: bchristi Date: 2019-11-04 19:42:39 +0000
04-11-2019
I updated the synoposis to make it explicit that this is a backout of JDK-8212117.
30-10-2019