A common interface defining methods for start/stop lifecycle control.
The typical use case for this is to control asynchronous processing.
NOTE: This interface does not imply specific auto-startup semantics.
Consider implementing
SmartLifecycle for that purpose.
Can be implemented by both components (typically a Spring bean defined in a
Spring context) and containers (typically a Spring
ApplicationContextitself). Containers will propagate start/stop signals to all components that
apply within each container, e.g. for a stop/restart scenario at runtime.
Can be used for direct invocations or for management operations via JMX.
In the latter case, the
org.springframework.jmx.export.MBeanExporterwill typically be defined with an
org.springframework.jmx.export.assembler.InterfaceBasedMBeanInfoAssembler,
restricting the visibility of activity-controlled components to the Lifecycle
interface.
Note that the present
Lifecycle interface is only supported on
top-level singleton beans. On any other component, the
Lifecycleinterface will remain undetected and hence ignored. Also, note that the extended
SmartLifecycle interface provides sophisticated integration with the
application context's startup and shutdown phases.