Byte Buddy
==========

<a href="https://bytebuddy.net">
<img src="https://raw.githubusercontent.com/raphw/byte-buddy/gh-pages/images/logo-bg.png" alt="Byte Buddy logo" height="180px" align="right" />
</a>

runtime code generation for the Java virtual machine

[![Actions Status](https://github.com/raphw/byte-buddy/workflows/CI/badge.svg)](https://github.com/raphw/byte-buddy/actions)
[![Security Score](https://snyk-widget.herokuapp.com/badge/mvn/net.bytebuddy/byte-buddy/badge.svg)](https://snyk.io/test/github/raphw/byte-buddy)
[![Coverage Status](https://img.shields.io/coveralls/raphw/byte-buddy/master.svg)](https://coveralls.io/r/raphw/byte-buddy?branch=master)
[![Maven Central](https://img.shields.io/maven-central/v/net.bytebuddy/byte-buddy)](https://central.sonatype.com/artifact/net.bytebuddy/byte-buddy)
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/6251/badge)](https://bestpractices.coreinfrastructure.org/projects/6251)

Byte Buddy is a code generation and manipulation library for creating and modifying Java classes during the runtime of a
Java application and without the help of a compiler. Other than the code generation utilities
that [ship with the Java Class Library](https://docs.oracle.com/javase/8/docs/api/java/lang/reflect/Proxy.html), Byte
Buddy allows the creation of arbitrary classes and is not limited to implementing interfaces for the creation of runtime
proxies. Furthermore, Byte Buddy offers a convenient API for changing classes either manually, using a Java agent or
during a build.

Java version compatibility
==========================

The following table lists the minimal versions of Byte Buddy that is required need to support a certain Java 
class file version without experimental support. The oldest supported Java version is Java 5, whereas class files
of any older version can be transformed. As of 1.17.0, support will extend to new Java versions unless previously
unknown class file features are discovered. This is possible through Byte Buddy's support of the Class File API. 

| Byte Buddy version | Supported Java version |
|--------------------|------------------------|
| 1.17.0             | 25+                    |
| 1.15.4             | 24                     |
| 1.14.12            | 23                     |
| 1.14.8             | 22                     |
| 1.14.3             | 21                     |
| 1.12.18            | 20                     |
| 1.12.9             | 19                     |
| 1.11.6             | 18                     |
| 1.10.19            | 17                     |

Usage
=====

In order to use Byte Buddy, one does not require an understanding of Java byte code or
the [class file format](https://docs.oracle.com/javase/specs/jvms/se8/html/jvms-4.html). In contrast, Byte Buddy’s API
aims for code that is concise and easy to understand for everybody. Nevertheless, Byte Buddy remains fully customizable
down to the possibility of defining custom byte code. Furthermore, the API was designed to be as non-intrusive as
possible and as a result, Byte Buddy does not leave any trace in the classes that were created by it. For this reason,
the generated classes can exist without requiring Byte Buddy on the class path. Because of this feature, Byte Buddy’s
mascot was chosen to be a ghost.

Byte Buddy is written in Java 5 but supports the generation of classes for any Java version. Byte Buddy is a
light-weight library and only depends on the visitor API of the Java byte code parser library
[ASM](https://asm.ow2.io/) which does itself
[not require any further dependencies](https://repo1.maven.org/maven2/org/ow2/asm/asm/5.0.4/asm-5.0.4.pom).

At first sight, runtime code generation can appear to be some sort of black magic that should be avoided and only few
developers write applications that explicitly generate code during their runtime. However, this picture changes when
creating libraries that need to interact with arbitrary code and types that are unknown at compile time. In this
context, a library implementer must often choose between either requiring a user to implement library-proprietary
interfaces or to generate code at runtime when the user’s types becomes first known to the library. Many known libraries
such as for example *Spring* or *Hibernate* choose the latter approach which is popular among their users under the term
of using [*Plain Old Java Objects*](https://en.wikipedia.org/wiki/Plain_Old_Java_Object). As a result, code generation
has become an ubiquitous concept in the Java space. Byte Buddy is an attempt to innovate the runtime creation of Java
types in order to provide a better tool set to those relying on code generation.

___

<a href="https://bytebuddy.net">
<img src="https://raw.githubusercontent.com/raphw/byte-buddy/gh-pages/images/dukeschoice.jpg" alt="Duke's Choice award" height="110px" align="left" />
</a>

In October 2015, Byte Buddy was distinguished with a
[*Duke's Choice award*](https://www.oracle.com/corporate/pressrelease/dukes-award-102815.html)
by Oracle. The award appreciates Byte Buddy for its "*tremendous amount of innovation in Java Technology*". We feel very
honored for having received this award and want to thank all users and everybody else who helped making Byte Buddy the
success it has become. We really appreciate it!

___

Byte Buddy offers excellent performance at production quality. It is stable and in use by distinguished frameworks and
tools such as [Mockito](https://site.mockito.org/), [Hibernate](https://hibernate.org/)
, [Jackson](https://github.com/FasterXML/jackson), [Google's Bazel build system](https://bazel.build/)
and [many others](https://github.com/raphw/byte-buddy/wiki/Projects-using-Byte-Buddy). Byte Buddy is also used by a
large number of commercial products to great result. It is currently downloaded over 75 million times a year.

Hello World
-----------

Saying *Hello World* with Byte Buddy is as easy as it can get. Any creation of a Java class starts with an instance of
the `ByteBuddy` class which represents a configuration for creating new types:

```java
Class<?> dynamicType = new ByteBuddy()
  .subclass(Object.class)
  .method(ElementMatchers.named("toString"))
  .intercept(FixedValue.value("Hello World!"))
  .make()
  .load(getClass().getClassLoader())
  .getLoaded();
assertThat(dynamicType.newInstance().toString(), is("Hello World!"));
```

The default `ByteBuddy` configuration which is used in the above example creates a Java class in the newest version of
the class file format that is understood by the processing Java virtual machine. As hopefully obvious from the example
code, the created type will extend the `Object` class and overrides its `toString` method which should return a fixed
value of `Hello World!`. The method to be overridden is identified by a so-called `ElementMatcher`. In the above
example, a predefined element matcher `named(String)` is used which identifies methods by their exact names. Byte Buddy
comes with numerous predefined and well-tested matchers which are collected in the `ElementMatchers`
class and which can be easily composed. The creation of custom matchers is however as simple as implementing the
([functional](https://docs.oracle.com/javase/8/docs/api/java/lang/FunctionalInterface.html)) `ElementMatcher` interface.

For implementing the `toString` method, the `FixedValue` class defines a constant return value for the overridden
method. Defining a constant value is only one example of many method interceptors that ship with Byte Buddy. By
implementing the `Implementation` interface, a method could however even be defined by custom byte code.

Finally, the described Java class is created and then loaded into the Java virtual machine. For this purpose, a target
class loader is required. Eventually, we can convince ourselves of the result by calling the `toString` method on an
instance of the created class and finding the return value to represent the constant value we expected.

A more complex example
----------------------

Of course, a *Hello World example* is a too simple use case for evaluating the quality of a code generation library. In
reality, a user of such a library wants to perform more complex manipulations, for example by introducing hooks into the
execution path of a Java program. Using Byte Buddy, doing so is however equally simple. The following example gives a
taste of how method calls can be intercepted.

Byte Buddy expresses dynamically defined method implementations by instances of the `Implementation` interface. In the
previous example, `FixedValue` that implements this interface was already demonstrated. By implementing this interface,
a user of Byte Buddy can go to the length of defining custom byte code for a method. Normally, it is however easier to
use Byte Buddy's predefined implementations such as `MethodDelegation` which allows for implementing any method in plain
Java. Using this implementation is straight forward as it operates by delegating the control flow to any POJO. As an
example of such a POJO, Byte Buddy can for example redirect a call to the only method of the following class:

```java
public class GreetingInterceptor {
  public Object greet(Object argument) {
    return "Hello from " + argument;
  }
}
```

Note that the above `GreetingInterceptor` does not depend on any Byte Buddy type. This is good news because none of the
classes that Byte Buddy generates require Byte Buddy on the class path! Given the above `GreetingInterceptor`, we can
use Byte Buddy to implement the Java 8 `java.util.function.Function` interface and its abstract `apply` method:

```java
Class<? extends java.util.function.Function> dynamicType = new ByteBuddy()
  .subclass(java.util.function.Function.class)
  .method(ElementMatchers.named("apply"))
  .intercept(MethodDelegation.to(new GreetingInterceptor()))
  .make()
  .load(getClass().getClassLoader())
  .getLoaded();
assertThat((String) dynamicType.newInstance().apply("Byte Buddy"), is("Hello from Byte Buddy"));
```

Executing the above code, Byte Buddy implements Java's `Function` interface and implements the `apply` method as a
delegation to an instance of the `GreetingInterceptor` POJO that we defined before. Now, every time that the
`Function::apply` method is called, the control flow is dispatched to `GreetingInterceptor::greet` and the latter
method's return value is returned from the interface's method.

Interceptors can be defined to take with more generic inputs and outputs by annotating the interceptor's parameters.
When Byte Buddy discovers an annotation, the library injects the dependency that the interceptor parameter requires. An
example for a more general interceptor is the following class:

```java
public class GeneralInterceptor {
  @RuntimeType
  public Object intercept(@AllArguments Object[] allArguments,
                          @Origin Method method) {
    // intercept any method of any signature
  }
}
```

With the above interceptor, any intercepted method could be matched and processed. For example, when matching
`Function::apply`, the method's arguments would be passed as the single element of an array. Also, a `Method`
reference to `Fuction::apply` would be passed as the interceptor's second argument due to the `@Origin`
annotation. By declaring the `@RuntimeType` annotation on the method, Byte Buddy finally casts the returned value to the
return value of the intercepted method if this is necessary. In doing so, Byte Buddy also applies automatic boxing and
unboxing.

Besides the annotations that were already mentioned there exist plenty of other predefined annotations. For example,
when using the `@SuperCall` annotation on a `Runnable` or `Callable` type, Byte Buddy injects proxy instances that allow
for an invocation of a non-abstract super method if such a method exists. And even if Byte Buddy does not cover a use
case, Byte Buddy offers an extension mechanism for defining custom annotations.

You might expect that using these annotations ties your code to Byte Buddy. However, Java ignores annotations in case
that they are not visible to a class loader. This way, generated code can still exist without Byte Buddy! You can find
more information on the `MethodDelegation` and on all of its predefined annotations in its *javadoc* and in Byte Buddy's
tutorial.

Changing existing classes
----------------------

Byte Buddy is not limited to creating subclasses but is also capable of redefining existing code. To do so, Byte Buddy
offers a convenient API for defining
so-called [Java agents](https://docs.oracle.com/javase/8/docs/api/java/lang/instrument/package-summary.html). Java
agents are plain old Java programs that can be used to alter the code of an existing Java application during its
runtime. As an example, we can use Byte Buddy to change methods to print their execution time. For this, we first define
an interceptor similar to the interceptors in the previous examples:

```java
public class TimingInterceptor {
  @RuntimeType
  public static Object intercept(@Origin Method method, 
                                 @SuperCall Callable<?> callable) {
    long start = System.currentTimeMillis();
    try {
      return callable.call();
    } finally {
      System.out.println(method + " took " + (System.currentTimeMillis() - start));
    }
  }
}
```

Using a Java agent, we can now apply this interceptor to all types that match an `ElementMatcher` for
a `TypeDescription`. For the example, we choose to add the above interceptor to all types with a name that ends
in `Timed`. This is done for the sake of simplicity whereas an annotation would probably be a more appropriate
alternative to mark such classes for a production agent. Using Byte Buddy's `AgentBuilder` API, creating a Java agent is
as easy as defining the following agent class:

```java
public class TimerAgent {
  public static void premain(String arguments, 
                             Instrumentation instrumentation) {
    new AgentBuilder.Default()
      .type(ElementMatchers.nameEndsWith("Timed"))
      .transform((builder, type, classLoader, module, protectionDomain) -> 
          builder.method(ElementMatchers.any())
                 .intercept(MethodDelegation.to(TimingInterceptor.class))
      ).installOn(instrumentation);
  }
}
```

Similar to Java's `main` method, the `premain` method is the entry point to any Java agent from which we apply the
redefinition. As one argument, a Java agent receives an instance of the `Instrumentation` interface which allows Byte
Buddy to hook into the JVM's standard API for runtime class redefinition.

This program is packaged together with a manifest file with
the [`Premain-Class` attribute](https://docs.oracle.com/javase/8/docs/api/java/lang/instrument/package-summary.html)
pointing to the `TimerAgent`. The resulting *jar* file can now be added to any Java application by
setting `-javaagent:timingagent.jar` similar to adding a jar to the class path. With the agent active, all classes
ending in `Timed` do now print their execution time to the console.

Byte Buddy is also capable of applying so-called runtime attachments by disabling class file format changes and using
the `Advice` instrumentation. Please refer to the *javadoc* of the `Advice` and the `AgentBuilder` class for further
information. Byte Buddy also offers the explicit change of Java classes via a `ByteBuddy` instance or by using the Byte
Buddy *Maven* and *Gradle* plugins.

Where to go from here?
----------------------

Byte Buddy is a comprehensive library and we only scratched the surface of Byte Buddy's capabilities. However, Byte
Buddy aims for being easy to use by providing a domain-specific language for creating classes. Most runtime code
generation can be done by writing readable code and without any knowledge of Java's class file format. If you want to
learn more about Byte Buddy, you can find such a [tutorial on Byte Buddy's web page](https://bytebuddy.net/#/tutorial) (
There is also [a Chinese translation available](https://notes.diguage.com/byte-buddy-tutorial/)).

Furthermore, Byte Buddy comes with a [detailed in-code documentation](https://bytebuddy.net/#/javadoc) and extensive
test case coverage which can also serve as example code. Finally, you can find an up-to-date list of articles and
presentations on Byte Buddy [in the wiki](https://github.com/raphw/byte-buddy/wiki/Web-Resources). When using Byte
Buddy, make also sure to read the following information on maintaining a project dependency.

Getting support
----------------------------

#### Commercial ####

The use of Byte Buddy is free and does not require the purchase of a license. To get the most out of the library or to
secure an easy start, it is however possible to purchase training, development hours or support plans. Rates are
dependent on the scope and duration of an engagement. Please get in touch with <rafael.wth@gmail.com> for further
information.

#### Tidelift ####

Byte Buddy
is [listed on Tidelift](https://tidelift.com/subscription/pkg/maven-net-bytebuddy-byte-buddy?utm_source=byte-buddy&utm_medium=referral)
. If you are not using Byte Buddy to an extent where you want to purchase explicit support and want to support the open
source community in general, please consider a subscription.

#### GitHub sponsors ####

You can support my work via [GitHub sponsors](https://github.com/sponsors/raphw). Note that this option is only meant
for commercial actors who are looking for a simple payment channel and that do not expect support in return. Support via
GitHub Sponsors is not possible to maintain VAT compliance. Please reach out for a direct support agreement instead.

#### Free ####

General questions can be asked on [Stack Overflow](https://stackoverflow.com/questions/tagged/byte-buddy) or on
the [Byte Buddy mailing list](https://groups.google.com/forum/#!forum/byte-buddy) which also serve as an archive for
questions. Of course, bug reports will be considered also outside of a commercial plan. For open source projects, it is
sometimes possible to receive extended help for taking Byte Buddy into use.

Dependency and API evolution
----------------------------

Byte Buddy is written on top of [ASM](https://asm.ow2.io), a mature and well-tested library for reading and writing
compiled Java classes. In order to allow for advanced type manipulations, Byte Buddy is intentionally exposing the ASM
API to its users. Of course, the direct use of ASM remains fully optional and most users will most likely never require
it. This choice was made such that a user of Byte Buddy is not restrained to its higher-level functionality but can
implement custom implementations without a fuss when it is necessary.

ASM has previously changed its public API but added a mechanism for API compatibility starting with version 4 of the
library. In order to avoid version conflicts with such older versions, Byte Buddy repackages the ASM dependency into its
own namespace. If you want to use ASM directly, the `byte-buddy-dep` artifact offers a version of Byte Buddy with an
explicit dependency to ASM. When doing so, you **must** repackage *both* Byte Buddy and ASM into your namespace to avoid
version conflicts.

Please note the [security policy](https://github.com/raphw/byte-buddy/blob/master/SECURITY.md) of this project.

Byte Buddy supports execution on all JVM versions from version five and onwards in a single jar. This is done to ease 
the development of Java agents which often require to support older, or unknown, applications which are not actively 
updated. To allow for this while also supporting modern Java and features like CDS or class validation with stack 
map frames, the main jars for Byte Buddy ship as multi-release jars that contain class files in version five and eight. 
As a result, the jar size of Byte Buddy is higher as one would expect. Jar file size is not normally a problem, as
the majority of Byte Buddy's classes will never be loaded. Yet, file size might be an issue when distributing Java 
agents. As agents already need to be bundled as a single jar, it is therefore recommended to remove either the basic 
Java five version, or the multi-release Java eight version of the contained class files, to reduce this issue. This 
is supported by most build plugins for this purpose, such as the
[Maven Shade plugin](https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#filters). Integration to the JDK's Class File API is contained in multi-release folders for version
24 and later. These folders can be stripped without consequence, other than loosing support for the Class File API.

License and development
-----------------------

Byte Buddy is licensed under the liberal and business-friendly
[*Apache Licence, Version 2.0*](https://www.apache.org/licenses/LICENSE-2.0.html) and is freely available on GitHub.
Additionally, the *byte-buddy* distribution bundles ASM which is released
under [a 3-clause BSD license](https://asm.ow2.io/license.html).

Byte Buddy binaries are published to the repositories of Maven Central and on JCenter. The artifacts signatures can be
validated against [this PGP public key](https://keys.openpgp.org/search?q=rafael.wth@gmail.com) beginning with Byte
Buddy 1.10.3. Older versions can be validated
against [this older and weaker certificate](https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xf42b96b8648b5c4a1c43a62fbb2914c1fa0811c3)
.

The project is built using <a href="https://maven.apache.org/">Maven</a>. From your shell, cloning and building the
project would go something like this:

```shell
git clone https://github.com/raphw/byte-buddy.git
cd byte-buddy
mvn package
```

On these commands, Byte Buddy is cloned from GitHub and built on your machine. Further build options are listed in the
root POM file. Byte Buddy can be built with any JDK of at least version 6. It is however recommended to use a JDK of 
at least version 8 as the builds for version 6 and 7 require the usage of unencrypted HTTP. Its support is only meant
for running tests against this JDK version and can expose you to man-in-the-middle attacks. Therefore, these builds 
should be avoided. Byte Buddy is currently tested for versions 6 and upwards of the JDK on CI servers.

Please use GitHub's [issue tracker](https://github.com/raphw/byte-buddy/issues) for reporting bugs. When committing
code, please provide test cases that prove the functionality of your features or that demonstrate a bug fix.
Furthermore, make sure you are not breaking any existing test cases. If possible, please take the time to write some
documentation. For feature requests or general feedback, you can also use the
[issue tracker](https://github.com/raphw/byte-buddy/issues) or contact us on
[our mailing list](https://groups.google.com/forum/#!forum/byte-buddy).

Supporters
----------

The work on Byte Buddy is also possible thanks to a row of supporters that have dedicated regular resources and
attention to the project. Please take your time to have a look at those supporters and their offerings.

<a href="https://www.scienta.no">
<img src="https://bytebuddy.net/logos/scienta.png" height="50" alt="Scienta AS"/> 
</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a href="https://www.instana.com">
<img src="https://bytebuddy.net/logos/instana.png" height="50" alt="Instana"/>
</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a href="https://www.sqreen.com">
<img src="https://bytebuddy.net/logos/sqreen.png" height="50" alt="Sqreen"/>
</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a href="https://www.elastic.co">
<img src="https://bytebuddy.net/logos/elastic.png" height="50" alt="Elastic"/>
</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a href="https://www.spotify.com">
<img src="https://bytebuddy.net/logos/spotify.png" height="50" alt="Spotify"/>
</a>
