CRaC Resource adapter for bean lifecycle in application context #30242
Assignees
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
Milestone
Comments
jhoeller
added
in: core
jhoeller
added a commit
that referenced
this issue
May 3, 2023
jhoeller
added a commit
that referenced
this issue
May 3, 2023
sdeleuze
added a commit
to sdeleuze/spring-framework
that referenced
this issue
May 4, 2023
RuntimeHintsAgentPlugin purpose is to verify that the reflective invocations expected match the ones performed. spring-projectsgh-30242 introduces a code path where the reflective invocation is skipped when running on native. This issue set the system property "org.graalvm.nativeimage.imagecode" to "runtime" when running runtime tests with the agent in order to make sure the code path tested for those tests is the native one. Closes spring-projectsgh-30422
sdeleuze
added a commit
to sdeleuze/spring-framework
that referenced
this issue
May 4, 2023
Skip CRaC support with native images to avoid compiling related infrastructure to the native image and to fix tests via spring-projectsgh-30422. See spring-projectsgh-30242
This was referenced Jun 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In addition to our CRaC-oriented revisiting of the existing contracts for the bean lifecycle in an application context (#29921), we consider providing an
org.crac.Resourceadapter for Spring'sDefaultLifecycleProcessorout of the box - e.g. as an implicit optional part of theDefaultLifecycleProcessorimplementation or as a dedicated subclass of it. This allows for stopping/restarting of beans in an application context on a fine-grained basis, with some tightening of theLifecyclecontract and possibly even some dedicated extensions inSmartLifecyclethat participating component implementations may rely on.The text was updated successfully, but these errors were encountered: