Using GraalVM Tracing Agent to configure the native application

The small native application we created in the previous recipe looks so promising that we’ve decided to build a bigger football application as a native app.

The application we created in the Creating a native image using Spring Boot recipe didn’t require any special configuration. But native applications are built AOT. That means the compiler needs to analyze all code statically and detect the code reached during runtime. There are some Java technologies, such as the Java Native Interface (JNI), Reflection, dynamic proxy objects, and class-path resources, that are very difficult to detect just by using static code analysis. The native compiler can use configuration files to include the required components in the final binary. As you may have figured out, the difficult part is configuring those files by detecting the components to be included in the final binary. For that purpose, GraalVM provides an agent...