Uses of Interface
org.springframework.context.Lifecycle
Packages that use Lifecycle
Package
Description
This package builds on the beans package to add support for
message sources and for the Observer design pattern, and the
ability for application objects to obtain resources using a
consistent API.
Annotation support for the Application Context, including JSR-250 "common"
annotations, component-scanning, and Java-based metadata for creating
Spring-managed objects.
Classes supporting the org.springframework.context package,
such as abstract base classes for ApplicationContext
implementations and a MessageSource implementation.
-
Uses of Lifecycle in org.springframework.context
Subinterfaces of Lifecycle in org.springframework.contextModifier and TypeInterfaceDescriptioninterface
SPI interface to be implemented by most if not all application contexts.interface
Strategy interface for processing Lifecycle beans within the ApplicationContext.interface
An extension of theLifecycle
interface for those objects that require to be started uponApplicationContext
refresh and/or shutdown in a particular order. -
Uses of Lifecycle in org.springframework.context.annotation
Classes in org.springframework.context.annotation that implement LifecycleModifier and TypeClassDescriptionclass
Standalone application context, accepting component classes as input — in particular@Configuration
-annotated classes, but also plain@Component
types and JSR-330 compliant classes usingjakarta.inject
annotations. -
Uses of Lifecycle in org.springframework.context.support
Classes in org.springframework.context.support that implement LifecycleModifier and TypeClassDescriptionclass
Abstract implementation of theApplicationContext
interface.class
Base class forApplicationContext
implementations which are supposed to support multiple calls toAbstractApplicationContext.refresh()
, creating a new internal bean factory instance every time.class
AbstractRefreshableApplicationContext
subclass that adds common handling of specified config locations.class
Convenient base class forApplicationContext
implementations, drawing configuration from XML documents containing bean definitions understood by anXmlBeanDefinitionReader
.class
Standalone XML application context, taking the context definition files from the class path, interpreting plain paths as class path resource names that include the package path (e.g.class
Spring's default implementation of theLifecycleProcessor
strategy.class
Standalone XML application context, taking the context definition files from the file system or from URLs, interpreting plain paths as relative file system locations (e.g.class
Generic ApplicationContext implementation that holds a single internalDefaultListableBeanFactory
instance and does not assume a specific bean definition format.class
AnApplicationContext
implementation that extendsGenericApplicationContext
and implementsGroovyObject
such that beans can be retrieved with the dot de-reference syntax instead of usingAbstractApplicationContext.getBean(java.lang.String)
.class
Convenient application context with built-in XML support.class
ApplicationContext
implementation which supports programmatic registration of beans and messages, rather than reading bean definitions from external configuration sources.Methods in org.springframework.context.support that return types with arguments of type LifecycleModifier and TypeMethodDescriptionDefaultLifecycleProcessor.getLifecycleBeans()
Retrieve all applicable Lifecycle beans: all singletons that have already been created, as well as all SmartLifecycle beans (even if they are marked as lazy-init).Methods in org.springframework.context.support with parameters of type Lifecycle