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.Resource adapter for Spring's DefaultLifecycleProcessor out of the box - e.g. as an implicit optional part of the DefaultLifecycleProcessor implementation 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 the Lifecycle contract and possibly even some dedicated extensions in SmartLifecycle that participating component implementations may rely on.