OpenJDK proposal would provide Java class file API

ByJosephine J. Romero

Jun 23, 2022 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
OpenJDK proposal would provide Java class file API

Java would get an API for processing Java course information, below a proposal afoot in the Java community.

The draft classfile API proposal phone calls for provision of an API for parsing, producing, and transforming Java course information. This classfile library to begin with would provide as an inner alternative for the ASM Java bytecode manipulation framework. Eventually, ASM would be eradicated entirely from the JDK.

The classfile API proposal notes that class file era, parsing, and instrumentation are ubiquitous in the Java ecosystem, with a lot of resources and libraries needing to procedure course files. Frameworks generally perform on-the-fly bytecode instrumentation. The JDK, the proposal states, need to deliver an precise, comprehensive, up-to-day, performant API for examining, producing, and reworking Java class documents.

Design goals and principles for the API consist of owning all class file entities, such as approaches and fields, represented by immutable objects. Consumer-driven navigation also is a objective. Motivating the contact for a Java classfile library are elements like:

  • JDK consolidation, with the JDK itself important in dealing with class information. And there is a delay inherent in the JDK’s use of ASM.
  • Edition skew concerning frameworks and running the JDK. Apps and frameworks processing course files usually bundle a classfile library such as ASM. But due to the fact new course file attributes can appear in any release of the JDK, apps and frameworks are far more frequently encountering class information that are newer than the library they are bundled with, resulting in runtime faults or in frameworks making an attempt to parse course file formats from the long run. Developers want a classfile library that will be up-to-date with operating the JDK.
  • The JVM and class file format now are evolving quicker than right before. Whilst some evolutions are simple, others are additional elaborate, these as Venture Valhalla bringing forth new bytecodes, field descriptors, and verification regulations.
  • The language has enhanced substantially given that ASM was penned.

Ideas get in touch with for in the beginning replacing ASM as a runtime dependency of the JDK without unacceptable reduction of functionality. One more intention would be to substitute the interior classreader library utilized by the compiler and JDK resources. At some point, a array of frameworks and programs should really be in a position to use the library as an alternate to ASM, cglib, and other bytecode libraries.

Copyright © 2022 IDG Communications, Inc.

Resource backlink