org.springframework.asm

Interface Summary
Interface Description

Opcodes
Defines the JVM opcodes, access flags and array type codes.

Interface Summary
Interface	Description
Opcodes	Defines the JVM opcodes, access flags and array type codes.

Class Summary
Class	Description
AnnotationVisitor	A visitor to visit a Java annotation.
AnnotationWriter	An `AnnotationVisitor` that generates annotations in bytecode form.
Attribute	A non standard class, field, method or code attribute.
ByteVector	A dynamically extensible vector of bytes.
ClassReader	A Java class parser to make a `ClassVisitor` visit an existing class.
ClassVisitor	A visitor to visit a Java class.
ClassWriter	A `ClassVisitor` that generates classes in bytecode form.
Context	Information about a class being parsed in a `ClassReader`.
CurrentFrame	Information about the input stack map frame at the "current" instruction of a method.
Edge	An edge in the control flow graph of a method body.
FieldVisitor	A visitor to visit a Java field.
FieldWriter	An `FieldVisitor` that generates Java fields in bytecode form.
Frame	Information about the input and output stack map frames of a basic block.
Handle	A reference to a field or a method.
Handler	Information about an exception handler block.
Item	A constant pool item.
Label	A label represents a position in the bytecode of a method.
MethodVisitor	A visitor to visit a Java method.
MethodWriter	A `MethodVisitor` that generates methods in bytecode form.
ModuleVisitor	A visitor to visit a Java module.
ModuleWriter
SpringAsmInfo	Utility class exposing constants related to Spring's internal repackaging of the ASM bytecode manipulation library (currently based on version 6.0).
Type	A Java field or method type.
TypePath	The path to a type argument, wildcard bound, array element type, or static inner type within an enclosing type.
TypeReference	A reference to a type appearing in a class, field or method declaration, or on an instruction.

Package org.springframework.asm Description

Spring's repackaging of ASM (for internal use only).

This repackaging technique avoids any potential conflicts with dependencies on ASM at the application level or from third-party libraries and frameworks.

As this repackaging happens at the class file level, sources and javadocs are not available here.