Support AOT registration of Spring Factories #27955
Assignees
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
theme: aot
An issue related to Ahead-of-time processing
Milestone
Comments
bclozel
added
in: core
philwebb
added a commit
that referenced
this issue
May 11, 2022
bclozel
removed
the
status: pending-design-work
bclozel
added a commit
that referenced
this issue
May 11, 2022
This commit forces the resolution of all declared constructors when registering `RuntimeHints` for Spring factories. Resolving constructors can throw additional `NoClassDefFoundError` at runtime and during native image compilation, if a type exposed by the constructor is missing from the current classloader. See gh-27955
sbrannen
added a commit
to sbrannen/spring-framework
that referenced
this issue
May 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As seen in #27753,
SpringFactoriesLoaderis currently supported in Spring Native through subtitutions and complex AOT processors.We'd like to improve
SpringFactoriesLoaderand allow static registration of Spring Factories, something our AOT processing could leverage and call early during application startup. Once a Factory type is registered with entries,SpringFactoriesLoadershould use this entry as a pre-warmed cache and never look for additional entries inspring.factoriesfiles, skipping all the resource loading and reflection operations.Instead of registering String instances as entries, this new contract might take
Supplierinstances instead, maybe mirroring the new contract to be added in #27954The text was updated successfully, but these errors were encountered: