Interface defining methods for start/stop lifecycle control.
The typical use case for this is to control asynchronous processing.
Can be implemented by both components (typically a Spring bean defined in
a Spring
org.springframework.beans.factory.BeanFactory ) and containers
(typically a Spring
ApplicationContext ). Containers will propagate
start/stop signals to all components that apply.
Can be used for direct invocations or for management operations via JMX.
In the latter case, the
org.springframework.jmx.export.MBeanExporter will typically be defined with an
org.springframework.jmx.export.assembler.InterfaceBasedMBeanInfoAssembler ,
restricting the visibility of activity-controlled components to the Lifecycle
interface.
author: Juergen Hoeller since: 2.0 See Also: ConfigurableApplicationContext See Also: org.springframework.jms.listener.AbstractMessageListenerContainer See Also: org.springframework.scheduling.quartz.SchedulerFactoryBean |