Spring Boot 4 Complete Guide · Pelajaran

Petunjuk Runtime untuk Reflection dan Resource

Daftarkan petunjuk reflection, proxy, dan resource agar fitur dinamis tetap berfungsi setelah kompilasi native.

Petunjuk Runtime untuk Reflection dan Resource adalah pelajaran Spring Boot 4 Complete Guide gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Spring Boot 4 Complete Guide, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Spring Boot 4 Complete Guide mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

Why Native Images Break Reflection

GraalVM native compilation uses closed-world analysis: at build time it must see every class, method, and field that could ever be reached. Code paths it cannot statically prove are reachable are removed from the final binary.

Reflection (Class.forName, getDeclaredMethod) hides the target from static analysis.
Dynamic proxies generated at runtime have no class to scan at build time.
Resources loaded via getResourceAsStream are not bundled unless declared.

The fix is to feed the analyzer explicit metadata called runtime hints, so it keeps these elements in the image.

What Spring Boot Contributes Automatically

Spring Boot 4 and the AOT (ahead-of-time) engine already register hints for most framework internals: @Component beans, @ConfigurationProperties classes, Jackson-bound DTOs reached through controllers, and auto-configuration classes.

You only write your own hints when you do something the AOT engine cannot trace, such as:

Reflectively instantiating a class you load by name from config.
Serializing a type that no controller or repository references.
Reading a non-classpath-scanned resource file at runtime.
Creating a JDK dynamic proxy for an interface you build yourself.

The RuntimeHintsRegistrar Interface

The primary programmatic entry point is RuntimeHintsRegistrar. You implement a single method, registerHints, which receives a RuntimeHints object exposing sub-registries for reflection, resources, proxies, serialization, and resource bundles.

The ClassLoader parameter lets you conditionally register only when a type is actually present on the classpath.

package com.example.demo.hints;

import org.springframework.aot.hint.RuntimeHints;
import org.springframework.aot.hint.RuntimeHintsRegistrar;

public class MyRuntimeHints implements RuntimeHintsRegistrar {

    @Override
    public void registerHints(RuntimeHints hints, ClassLoader classLoader) {
        // reflection, resources and proxies are registered here
    }
}

Registering Reflection Hints

Use hints.reflection().registerType(...) and pass the member categories you need. Categories are coarse-grained switches that tell GraalVM which members to keep reflectively accessible.

INVOKE_DECLARED_CONSTRUCTORS — keep constructors callable.
INVOKE_DECLARED_METHODS — keep methods invokable.
DECLARED_FIELDS — keep fields readable/writable.

Grant only what you actually use; over-broad hints bloat the image.

import org.springframework.aot.hint.MemberCategory;
import org.springframework.aot.hint.RuntimeHints;
import org.springframework.aot.hint.RuntimeHintsRegistrar;

public class ReflectionHints implements RuntimeHintsRegistrar {

    @Override
    public void registerHints(RuntimeHints hints, ClassLoader classLoader) {
        hints.reflection().registerType(
            com.example.demo.PaymentProcessor.class,
            MemberCategory.INVOKE_DECLARED_CONSTRUCTORS,
            MemberCategory.INVOKE_DECLARED_METHODS);
    }
}

Activating Hints with @ImportRuntimeHints

A registrar does nothing until Spring is told to run it. Annotate any configuration or component class with @ImportRuntimeHints, referencing your registrar. The AOT engine then invokes it during the build.

Place it next to the code that needs the hint so the relationship stays discoverable.

import org.springframework.context.annotation.Configuration;
import org.springframework.context.annotation.ImportRuntimeHints;

@Configuration
@ImportRuntimeHints(ReflectionHints.class)
public class PaymentConfig {
    // beans that rely on reflective access to PaymentProcessor
}

Conditional Registration with TypeReference

If a class might be absent at build time, register it by name using TypeReference instead of a hard .class literal. Combine with a presence check so the hint is only added when the type is on the classpath.

This pattern is common in starter libraries that adapt to optional dependencies.

import org.springframework.aot.hint.MemberCategory;
import org.springframework.aot.hint.RuntimeHints;
import org.springframework.aot.hint.RuntimeHintsRegistrar;
import org.springframework.aot.hint.TypeReference;
import org.springframework.util.ClassUtils;

public class OptionalHints implements RuntimeHintsRegistrar {

    @Override
    public void registerHints(RuntimeHints hints, ClassLoader classLoader) {
        if (ClassUtils.isPresent("com.example.optional.LegacyAdapter", classLoader)) {
            hints.reflection().registerType(
                TypeReference.of("com.example.optional.LegacyAdapter"),
                MemberCategory.INVOKE_DECLARED_CONSTRUCTORS);
        }
    }
}

Registering Resource Hints

Files loaded with getResourceAsStream or ClassPathResource must be declared, or they vanish from the native binary. Register exact paths or glob-style patterns through hints.resources().

registerPattern("config/*.json") — include matching classpath resources.
registerResource(...) — include a single known Resource.

import org.springframework.aot.hint.RuntimeHints;
import org.springframework.aot.hint.RuntimeHintsRegistrar;

public class ResourceHints implements RuntimeHintsRegistrar {

    @Override
    public void registerHints(RuntimeHints hints, ClassLoader classLoader) {
        hints.resources()
             .registerPattern("templates/email/*.html")
             .registerPattern("data/countries.json");
    }
}

Registering Proxy Hints

JDK dynamic proxies created with Proxy.newProxyInstance need every implemented interface declared, because GraalVM must generate the proxy class at build time. Use hints.proxies().registerJdkProxy(...) with the full interface set.

Spring registers proxies for its own @Transactional and repository interfaces automatically; you only add hints for proxies you create yourself.

import org.springframework.aot.hint.RuntimeHints;
import org.springframework.aot.hint.RuntimeHintsRegistrar;

public class ProxyHints implements RuntimeHintsRegistrar {

    @Override
    public void registerHints(RuntimeHints hints, ClassLoader classLoader) {
        hints.proxies().registerJdkProxy(
            com.example.demo.AuditLog.class,
            com.example.demo.Versioned.class);
    }
}

A Complete Multi-Category Registrar

Real registrars usually combine several hint types. Here a single registrar declares reflection for a dynamically loaded strategy, a resource pattern for its config, and a proxy for an interface the app wires at runtime.

Keeping related hints together documents exactly which dynamic features a feature depends on.

import org.springframework.aot.hint.MemberCategory;
import org.springframework.aot.hint.RuntimeHints;
import org.springframework.aot.hint.RuntimeHintsRegistrar;
import org.springframework.aot.hint.TypeReference;

public class StrategyHints implements RuntimeHintsRegistrar {

    @Override
    public void registerHints(RuntimeHints hints, ClassLoader classLoader) {
        hints.reflection().registerType(
            TypeReference.of("com.example.demo.JsonExportStrategy"),
            MemberCategory.INVOKE_DECLARED_CONSTRUCTORS,
            MemberCategory.INVOKE_DECLARED_METHODS);

        hints.resources().registerPattern("strategies/*.properties");

        hints.proxies().registerJdkProxy(
            com.example.demo.ExportStrategy.class);
    }
}

Hinting Serialization with @RegisterReflectionForBinding

For DTOs that are only reached reflectively (for example via a manually built ObjectMapper outside any controller), the convenience annotation @RegisterReflectionForBinding registers all members needed for Jackson binding in one line, avoiding hand-listing categories.

It is a shortcut that delegates to the same reflection registry under the hood.

import org.springframework.aot.hint.annotation.RegisterReflectionForBinding;
import org.springframework.stereotype.Component;

@Component
@RegisterReflectionForBinding({ InvoiceDto.class, LineItemDto.class })
public class InvoiceExporter {
    // serializes InvoiceDto with a hand-built ObjectMapper
}

Verifying Hints Before Going Native

Compiling a native image is slow, so verify hints on the JVM first. The GraalVM reachability metadata agent records actual reflection/resource access during a normal test run and emits JSON metadata you can compare against your hints.

Spring also offers RuntimeHintsPredicates to assert in a unit test that a given type or resource is registered — fast feedback without a full native build.

import org.junit.jupiter.api.Test;
import org.springframework.aot.hint.RuntimeHints;
import org.springframework.aot.hint.predicate.RuntimeHintsPredicates;
import static org.assertj.core.api.Assertions.assertThat;

class ReflectionHintsTest {

    @Test
    void registersPaymentProcessor() {
        RuntimeHints hints = new RuntimeHints();
        new ReflectionHints().registerHints(hints, getClass().getClassLoader());

        assertThat(RuntimeHintsPredicates.reflection()
                .onType(com.example.demo.PaymentProcessor.class))
            .accepts(hints);
    }
}

Quick Check: Proxy Hints

Your application creates a JDK dynamic proxy for two of your own interfaces using Proxy.newProxyInstance. It works on the JVM but throws at runtime in the native image. Which hint fixes it?

Recap

GraalVM's closed-world analysis strips anything it cannot statically prove reachable, so dynamic features need explicit runtime hints.

Implement RuntimeHintsRegistrar.registerHints and activate it with @ImportRuntimeHints.
hints.reflection().registerType(...) with the right MemberCategory values keeps reflective constructors, methods, and fields.
hints.resources().registerPattern(...) bundles runtime-loaded files.
hints.proxies().registerJdkProxy(...) declares custom JDK dynamic proxies.
@RegisterReflectionForBinding is a shortcut for serialization DTOs.
Verify with RuntimeHintsPredicates and the reachability metadata agent before a costly native build.

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Petunjuk Runtime untuk Reflection dan Resource” gratis?

Ya — teks lengkap “Petunjuk Runtime untuk Reflection dan Resource” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Spring Boot 4 Complete Guide, upgrade ke CoddyKit PRO. Kursus Spring Boot 4 Complete Guide mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Petunjuk Runtime untuk Reflection dan Resource”?

Daftarkan petunjuk reflection, proxy, dan resource agar fitur dinamis tetap berfungsi setelah kompilasi native. Kamu berlatih Spring Boot 4 Complete Guide dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Spring Boot 4 Complete Guide?

Tidak diperlukan pengalaman sebelumnya. Spring Boot 4 Complete Guide di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.

Berapa lama pelajaran “Petunjuk Runtime untuk Reflection dan Resource” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Spring Boot 4 Complete Guide ini?

Ya. Setiap pelajaran Spring Boot 4 Complete Guide menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

Pemrosesan AOT dan Pipeline Build Native
Petunjuk Runtime untuk Reflection dan Resource
Berbagi Data Class dan Penyetelan Startup JVM
Mendiagnosis dan Memperbaiki Masalah Kompatibilitas Native

← Kembali ke Spring Boot 4 Complete Guide