Uses of Package
net.bytebuddy.dynamic.scaffold
Packages that use net.bytebuddy.dynamic.scaffold
Package
Description
Byte Buddy is a library for creating Java classes at runtime of a Java program.
An agent builder is used to easily implement load-time class-transformations using a Java agent.
The ASM package contains classes that are meant for direct interaction with the ASM API.
This package contains classes and interfaces that are connected to writing the byte stream that represents a Java
type that is dynamically created and for loading this type into a running JVM process.
This package contains helper types and implementations that are responsible for the actual writing of a byte array
representing a Java class.
All classes and types in this package are related to creating a
DynamicType
by
enhancing a given type.All classes and types in this package are related to creating a
DynamicType
by
creating a subclass of a given type.The implementation package contains any logic for intercepting method calls.
Auxiliary types describe helper types that aid as a supplementary to a given
InstrumentedType
.This package contains annotations, types and classes that are responsible for binding a method to calling another
method by interpreting annotations that indicate how a method should be bound to another method.
-
Classes in net.bytebuddy.dynamic.scaffold used by net.bytebuddyClassDescriptionA class writer strategy is responsible for the creation of a
ClassWriter
when creating a type.Implementations of this interface represent an instrumented type that is subject to change.A factory for creating anInstrumentedType
.Implementations are able to prepare anInstrumentedType
.A compiler to produce aMethodGraph
from a given type.A method registry is responsible for storing information on how a method is intercepted.If type validation is enabled, Byte Buddy performs several checks to ensure that a generated class file is specified in a valid manner. -
Classes in net.bytebuddy.dynamic.scaffold used by net.bytebuddy.agent.builderClassDescriptionImplementations of this interface represent an instrumented type that is subject to change.Implementations are able to prepare an
InstrumentedType
. -
Classes in net.bytebuddy.dynamic.scaffold used by net.bytebuddy.asmClassDescriptionA field locator offers an interface for locating a field that is declared by a specified type.Implementations of this interface represent an instrumented type that is subject to change.Implementations are able to prepare an
InstrumentedType
.A compiler to produce aMethodGraph
from a given type. -
Classes in net.bytebuddy.dynamic.scaffold used by net.bytebuddy.dynamicClassDescriptionA class writer strategy is responsible for the creation of a
ClassWriter
when creating a type.A field registry represents an extendable collection of fields which are identified by their names that are mapped to a givenFieldAttributeAppender
.Implementations represent anInstrumentedType
with a flexible name.A compiler to produce aMethodGraph
from a given type.A method registry is responsible for storing information on how a method is intercepted.A handler for implementing a method.A record component registry represents an extendable collection of record components which are identified by their names that are mapped to a givenRecordComponentAttributeAppender
.A type initializer is responsible for defining a type's static initialization block.If type validation is enabled, Byte Buddy performs several checks to ensure that a generated class file is specified in a valid manner.A type writer is a utility for writing an actual class file using the ASM library. -
Classes in net.bytebuddy.dynamic.scaffold used by net.bytebuddy.dynamic.scaffoldClassDescriptionA class writer strategy is responsible for the creation of a
ClassWriter
when creating a type.Default implementations of class writer strategies.A field locator offers an interface for locating a field that is declared by a specified type.An abstract base implementation of a field locator.A factory for creating aFieldLocator
.A factory for creating aFieldLocator.ForClassHierarchy
.A factory for locating a field in a top-level type.A field locator that never discovers a field.A resolution for a field lookup.An illegal resolution.A field registry represents an extendable collection of fields which are identified by their names that are mapped to a givenFieldAttributeAppender
.Represents a compiled field registry.A no-op field registry that does not register annotations for any field.An entry of a compiled field registry.An entry of the default field registry.Implementations of this interface represent an instrumented type that is subject to change.A factory for creating anInstrumentedType
.Default implementations of instrumented type factories.Implementations are able to prepare anInstrumentedType
.A prepareable that does not alter the instrumented type.Implementations represent anInstrumentedType
with a flexible name.A method graph represents a view on a set of methods as they are seen from a given type.A compiler to produce aMethodGraph
from a given type.An abstract base implementation of a method graph compiler.A harmonizer is responsible for creating a token that identifies a method's relevant attributes for considering two methods of being equal or not.A harmonizer for the Java programming language that identifies a method by its parameter types only.A token that identifies a Java method's type by its parameter types only.A harmonizer for the Java virtual machine's method dispatching rules that identifies a method by its parameter types and return type.A token that identifies a Java method's type by its parameter types and return type.A key represents a collection of methods within a method graph to later yield a node representing a collection of methods, i.e.A detached version of a key that identifies methods by their JVM signature, i.e.A harmonized key represents a key where equality is decided based on tokens that are returned by aMethodGraph.Compiler.Default.Harmonizer
.A store for collected methods that are identified by keys.An entry of a key store.Implementations are responsible for identifying a representative method for aMethodGraph.Node
between several ambiguously resolved methods.A directional merger that always returns either the left or right method description.A flat compiler that simply returns the methods that are declared by the instrumented type.A canonical implementation of an empty method graph.A linked method graph represents a view that additionally exposes information of a given type's super type view and a view on this graph's directly implemented interfaces.Represents a node within a method graph.Represents aMethodGraph.Node
's state.A canonical implementation of an unresolved node.A list of nodes.A method registry is responsible for storing information on how a method is intercepted.A compiled version of a method registry.An entry of a compiled method registry.An entry of a default method registry.An entry of a prepared method registry.A handler for implementing a method.A compiled handler for implementing a method.A handler for defining an abstract or native method.A compiled handler for implementing a method.A handler for implementing a visibility bridge.A compiled handler for a visibility bridge handler.A method registry that fully prepared the instrumented type.A record component registry represents an extendable collection of record components which are identified by their names that are mapped to a givenRecordComponentAttributeAppender
.Represents a compiled record component registry.A no-op record component registry that does not register annotations for any record component.An entry of a compiled record component registry.An entry of the default record component registry.A type initializer is responsible for defining a type's static initialization block.A drain for writing a type initializer.A default implementation of a type initializer drain that creates a initializer method.Canonical implementation of a non-defined type initializer.If type validation is enabled, Byte Buddy performs several checks to ensure that a generated class file is specified in a valid manner.A type writer is a utility for writing an actual class file using the ASM library.A default implementation of aTypeWriter
.A dispatcher for dumping class files to the file system.A disabled dispatcher that does not dump any class files.A type writer that inlines the created type into an existing class file.A context registry allows to extract auxiliary types from a lazily created implementation context.An initialization handler is responsible for handling the creation of the type initializer.An initialization handler that appends code to a previously visited type initializer.A frame writer is responsible for adding empty frames on jump instructions.A frame writer that creates an expanded frame.A non-operational frame writer.An initialization handler that appends code to a previously visited type initializer with allowing activeTypeInitializer
registrations.An initialization handler that appends code to a previously visited type initializer without allowing activeTypeInitializer
registrations.A key to represent a unique signature.An unresolved type.A constraint for members that are legal for a given type.Represents the constraint of an annotation type.Represents the constraint of a class type.Represents the constraint of an interface type.Represents the constraint of a package type.Represents the constraint of a record type.An field pool that allows a lookup for how to implement a field.A field pool that does not allow any look ups.An entry of a field pool that describes how a field is implemented.An method pool that allows a lookup for how to implement a method.An entry of a method pool that describes how a method is implemented.A base implementation of an abstract entry that defines a method.The sort of an entry.An record component pool that allows a lookup for how to implement a record component.A record component pool that does not allow any look ups.An entry of a record component pool that describes how a record component is implemented. -
Classes in net.bytebuddy.dynamic.scaffold used by net.bytebuddy.dynamic.scaffold.inlineClassDescriptionA class writer strategy is responsible for the creation of a
ClassWriter
when creating a type.A field registry represents an extendable collection of fields which are identified by their names that are mapped to a givenFieldAttributeAppender
.Implementations represent anInstrumentedType
with a flexible name.A compiler to produce aMethodGraph
from a given type.A linked method graph represents a view that additionally exposes information of a given type's super type view and a view on this graph's directly implemented interfaces.Represents a node within a method graph.A method registry is responsible for storing information on how a method is intercepted.A record component registry represents an extendable collection of record components which are identified by their names that are mapped to a givenRecordComponentAttributeAppender
.If type validation is enabled, Byte Buddy performs several checks to ensure that a generated class file is specified in a valid manner.A type writer is a utility for writing an actual class file using the ASM library. -
Classes in net.bytebuddy.dynamic.scaffold used by net.bytebuddy.dynamic.scaffold.subclassClassDescriptionA class writer strategy is responsible for the creation of a
ClassWriter
when creating a type.A field registry represents an extendable collection of fields which are identified by their names that are mapped to a givenFieldAttributeAppender
.Implementations of this interface represent an instrumented type that is subject to change.Implementations represent anInstrumentedType
with a flexible name.A compiler to produce aMethodGraph
from a given type.A linked method graph represents a view that additionally exposes information of a given type's super type view and a view on this graph's directly implemented interfaces.A method registry is responsible for storing information on how a method is intercepted.A record component registry represents an extendable collection of record components which are identified by their names that are mapped to a givenRecordComponentAttributeAppender
.If type validation is enabled, Byte Buddy performs several checks to ensure that a generated class file is specified in a valid manner.A type writer is a utility for writing an actual class file using the ASM library. -
Classes in net.bytebuddy.dynamic.scaffold used by net.bytebuddy.implementationClassDescriptionA field locator offers an interface for locating a field that is declared by a specified type.A factory for creating a
FieldLocator
.Implementations of this interface represent an instrumented type that is subject to change.Implementations are able to prepare anInstrumentedType
.A compiler to produce aMethodGraph
from a given type.A linked method graph represents a view that additionally exposes information of a given type's super type view and a view on this graph's directly implemented interfaces.Represents a node within a method graph.A type initializer is responsible for defining a type's static initialization block.A drain for writing a type initializer.An entry of a method pool that describes how a method is implemented.A base implementation of an abstract entry that defines a method.The sort of an entry. -
Classes in net.bytebuddy.dynamic.scaffold used by net.bytebuddy.implementation.auxiliaryClassDescriptionImplementations of this interface represent an instrumented type that is subject to change.Implementations are able to prepare an
InstrumentedType
.A compiler to produce aMethodGraph
from a given type.A linked method graph represents a view that additionally exposes information of a given type's super type view and a view on this graph's directly implemented interfaces. -
Classes in net.bytebuddy.dynamic.scaffold used by net.bytebuddy.implementation.bind.annotationClassDescriptionImplementations of this interface represent an instrumented type that is subject to change.Implementations are able to prepare an
InstrumentedType
.