Package io.smallrye.classfile.constantpool
Provides interfaces describing constant pool entries for the io.smallrye.classfile library.
The io.smallrye.classfile.constantpool package contains interfaces describing constant pool entries in the
class file format. Constant pool entries are low-level models to faithfully represent the exact structure
of a class file.
APIs in this package perform null and unrepresentable argument checks, unless otherwise noted.
Reading the constant pool entries
When read fromclass files, the pool entries are lazily inflated; the contents of these entries, besides the
bare structure, are not evaluated to speed up parsing. Entries to users interest, usually accessed from other models
and elements, have their contents read on demand. For example, to search for methods, a user should filter first by
access flags and then by method name, and use equalsString(String) instead of checking equality
against stringValue(). This avoids inflation of UTF-8 entries as much as possible:
invalid @snippet
file not found on source path or snippet path: PackageSnippets.java
The entries also define accessors to validated symbolic information with nominal descriptor abstractions from the
java.lang.constant package. These symbolic information accessors perform validation against the read
class files, and throw IllegalArgumentException when the accessed constant pool entry contains
invalid data. The nominal descriptors represent validated data, which saves users from extra validations in future
processing.
Due to the lazy nature of class file parsing, IllegalArgumentException indicating malformed
class file data can be thrown at any method invocation. For example, an exception may come from a ClassEntry when it is first read from the constant pool (referring to an invalid index or wrong type of entry), when
its referred UTF-8 entry is expanded (malformed UTF-8 data), or when its symbolic information is accessed (the string
is not valid for a class entry).
Writing the constant pool entries
In general, users do not need to worry about working with the constant pool and its entries when writing
class files. Most Class-File API models and elements have two sets of factory methods: one that accepts symbolic
information representing the uses, and another that accepts constant pool entries. The constant pool builder
associated with class file builders, ClassFileBuilder.constantPool(), automatically creates or reuses
pool entries from the symbolic information. Validated data in symbolic information helps class file
generation by avoiding extraneous parsing of raw constant pool entry data.
As always, users can use factories that accept constant pool entries if they already have them by hand, or if they
desire fine-grained control over class file generation.
If many models and elements are reused from another ClassModel in class building, the class building process
can use a constant pool builder that extends from the given ClassModel, available through ConstantPoolBuilder::of(ClassModel), so that byte data with constant pool
references can be copied in batch, speeding up class building. This is especially applicable to class transformations,
and ConstantPoolSharingOption exists to control this behavior.
- Since:
- 24
-
ClassDescriptionMarker interface for constant pool entries that can represent constant values associated with elements of annotations.Models a
CONSTANT_Class_infostructure, representing a reference type, in the constant pool of aclassfile.Models aCONSTANT_Dynamic_infostructure, representing a dynamically-computed constant, in the constant pool of aclassfile.Provides read access to the constant pool and the bootstrap method table of aclassfile.Builder for the constant pool of aclassfile.Thrown to indicate that requested entry cannot be obtained from the constant pool or the bootstrap method table.Marker interface for constant pool entries that can represent constant values in theConstantValueattribute.Models aCONSTANT_Double_infostructure, representing adoubleconstant, in the constant pool of aclassfile.Superinterface modeling dynamically-computed constant pool entries, which includeConstantDynamicEntryandInvokeDynamicEntry, in the constant pool of aclassfile.Models aCONSTANT_Fieldref_infostructure, or a symbolic reference to a field, in the constant pool of aclassfile.Models aCONSTANT_Float_infostructure, or afloatconstant, in the constant pool of aclassfile.Models aCONSTANT_Integer_infostructure, or anintconstant, in the constant pool of aclassfile.Models aCONSTANT_InterfaceMethodRef_infostructure, or a symbolic reference to an interface method, in the constant pool of aclassfile.Models aCONSTANT_InvokeDynamic_infostructure, or the symbolic reference to a dynamically-computed call site, in the constant pool of aclassfile.Marker interface for constant pool entries suitable for loading via theldcinstructions.Models aCONSTANT_Long_infostructure, or alongconstant, in the constant pool of aclassfile.Superinterface modeling symbolic references to a member of a class or interface in the constant pool of aclassfile, which include references to fields, class methods, and interface methods.Models aCONSTANT_MethodHandle_infostructure, or a symbolic reference to a method handle, in the constant pool of aclassfile.Models aCONSTANT_MethodRef_infostructure, or a symbolic reference to a class method, in the constant pool of aclassfile.Models aCONSTANT_MethodType_infostructure, or a symbolic reference to a method type, in the constant pool of aclassfile.Models aCONSTANT_Module_infostructure, denoting a module, in the constant pool of aclassfile.Models aCONSTANT_NameAndType_infostructure, representing a field or method, in the constant pool of aclassfile.Models aCONSTANT_Package_info, representing a package, in the constant pool of aclassfile.Models an entry in the constant pool of aclassfile.Models aCONSTANT_String_infostructure, or a string constant, in the constant pool of aclassfile.Models aCONSTANT_UTF8_infoconstant, representing strings, in the constant pool of aclassfile.