Add a way to register the need for runtime reflection, resources, proxying, and serialization on components #27829
Assignees
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
theme: aot
An issue related to Ahead-of-time processing
type: enhancement
A general enhancement
Milestone
Comments
snicoll
added
type: enhancement
jhoeller
added
the
in: core
snicoll
added a commit
to snicoll/spring-framework
that referenced
this issue
Jan 6, 2022
This commit provides an API to record the need for reflection, resources, serialization, and proxies at runtime. It offers a central `RuntimeHints` facility that can record various aspects. For reflection, individual elements of a type can be recorded, as well as a predefined categories (identified by the `MemberCategory` enum). A method or constructor hint can refine whether the need to execute it is required. For resources, they can be included using includes/excludes pattern that can either: * An exact match: `com/example/test.properties` * A pattern, using `*` or `?` to include multiple resources, such as `com/example/*.properties` * A regular expression Resource bundles can be added as well by providing its basename. // TODO serialization - proxy Closes spring-projectsgh-27829
snicoll
added a commit
that referenced
this issue
Feb 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spring Native has a component called
NativeConfigurationRegistrythat offers a programmatic API to register the need for reflection, resources that are to be shipped in the native image, proxies as well as classes that should beSerializable.We'd like to revisit this contract and make less native specific as we believe that such information could be useful elsewhere.
Such an infrastructure could land in
spring-coreas it is rather high-level and focused on classes and resources. The actual processing of the registry, for instance, to write GraalVM-specific configuration files is not in the scope of this issue.The text was updated successfully, but these errors were encountered: