Class ContainerLifeCycle
- All Implemented Interfaces:
Container,Destroyable,Dumpable,Dumpable.DumpableContainer,LifeCycle
- Direct Known Subclasses:
AbstractConnectionFactory,AbstractConnectionPool,AbstractConnector,AbstractHandler,AbstractHttpClientTransport,AbstractLoginService,AbstractSessionCache,AbstractSessionDataStore,AdaptiveExecutionStrategy,AttributeContainerMap,CachingSessionDataStore,ClientConnectionFactory.Info,ClientConnectionFactoryOverHTTP2,ClientConnectionFactoryOverHTTP3,ClientConnector,ClientConnector.Configurator,CompressionPool,ConfigurableSpnegoLoginService,CustomRequestLog,DefaultSessionIdManager,DelegatingThreadPool,DeploymentManager,ExecutorThreadPool,HTTP2Client,HTTP2Session,HTTP3Client,HttpClient,HttpDestination,JAASLoginService,JakartaWebSocketContainer,JakartaWebSocketShutdownContainer,JettyWebSocketFrameHandlerFactory,JettyWebSocketServerContainer,KeyStoreScanner,LeakTrackingByteBufferPool,LowResourceMonitor,ManagedSelector,OpenIdConfiguration,OpenIdLoginService,ProtocolSession,QueuedThreadPool,QuicSession,Scanner,ScanningAppProvider,SelectorManager,ServletContextHandler.ServletContainerInitializerStarter,ServletTester,WebSocketClient,WebSocketComponents,WebSocketCoreClient
LifeCycle implementation for a collection of contained beans.
Beans can be added to the ContainerLifeCycle either as managed beans or as unmanaged beans.
A managed bean is started, stopped and destroyed with the aggregate.
An unmanaged bean is associated with the aggregate for the purposes of dump(), but its
lifecycle must be managed externally.
When a LifeCycle bean is added without a managed state being specified the state is
determined heuristically:
- If the added bean is running, it will be added as an unmanaged bean.
- If the added bean is !running and the container is !running, it will be added as an AUTO bean (see below).
- If the added bean is !running and the container is starting, it will be added as a managed bean and will be started (this handles the frequent case of new beans added during calls to doStart).
- If the added bean is !running and the container is started, it will be added as an unmanaged bean.
When stopping the container, a contained bean will be stopped by this aggregate only if it is started by this aggregate.
The methods addBean(Object, boolean), manage(Object) and unmanage(Object) can be used to
explicitly control the life cycle relationship.
If adding a bean that is shared between multiple ContainerLifeCycle instances, then it should be started
before being added, so it is unmanaged, or the API must be used to explicitly set it as unmanaged.
All EventListeners added via addEventListener(EventListener) are also added as beans and all beans
added via an addBean(Object) method that are also EventListeners are added as listeners via a
call to addEventListener(EventListener).
This class also provides utility methods to dump deep structures of objects. In the dump, the following symbols are used to indicate the type of contained object:
SomeContainerLifeCycleInstance +- contained POJO instance += contained MANAGED object, started and stopped with this instance +~ referenced UNMANAGED object, with separate lifecycle +? referenced AUTO object that could become MANAGED or UNMANAGED.
-
Nested Class Summary
Nested classes/interfaces inherited from class org.eclipse.jetty.util.component.AbstractLifeCycle
AbstractLifeCycle.AbstractLifeCycleListener, AbstractLifeCycle.StopExceptionNested classes/interfaces inherited from interface org.eclipse.jetty.util.component.Container
Container.InheritedListener, Container.ListenerNested classes/interfaces inherited from interface org.eclipse.jetty.util.component.Dumpable
Dumpable.DumpableContainerNested classes/interfaces inherited from interface org.eclipse.jetty.util.component.LifeCycle
LifeCycle.Listener -
Field Summary
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionbooleanAdds the given bean, detecting whether to manage it or not.booleanAdds the given bean, explicitly managing it or not.booleanaddEventListener(EventListener listener) Add an event listener.voidaddManaged(LifeCycle lifecycle) Adds a managed lifecycle.booleanvoiddestroy()Destroys the managed Destroyable beans in the reverse order they were added.protected voiddoStart()Starts the managed lifecycle beans in the order they were added.protected voiddoStop()Stops the managed lifecycle beans in the reverse order they were added.dump()voiddump(Appendable out) Dump this object to an Appendable with no indent.voiddump(Appendable out, String indent) Dump this object (and children) into an Appendable using the provided indent after any new lines.protected voiddumpObjects(Appendable out, String indent, Object... items) Dump this object, it's contained beans and additional items to an AppendablevoidDumps toSystem.err.<T> TgetBeans()<T> Collection<T><T> Collection<T>getContainedBeans(Class<T> clazz) protected <T> voidgetContainedBeans(Class<T> clazz, Collection<T> beans) booleanbooleanTest if this container manages a beanbooleanisUnmanaged(Object bean) voidManages a bean already contained by this aggregate, so that it is started/stopped/destroyed with this aggregate.booleanremoveBean(Object o) Removes the given bean.voidRemoves all beanbooleanremoveEventListener(EventListener listener) Remove an event listener.voidsetBeans(Collection<Object> beans) protected voidStarts the given lifecycle.protected voidStops the given lifecycle.voidUnmanages a bean already contained by this aggregate, so that it is not started/stopped/destroyed with this aggregate.voidupdateBean(Object oldBean, Object newBean) voidupdateBean(Object oldBean, Object newBean, boolean managed) voidupdateBeans(Object[] oldBeans, Object[] newBeans) voidupdateBeans(Collection<?> oldBeans, Collection<?> newBeans) Methods inherited from class org.eclipse.jetty.util.component.AbstractLifeCycle
getEventListeners, getState, getState, isFailed, isRunning, isStarted, isStarting, isStopped, isStopping, setEventListeners, start, stop, toStringMethods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitMethods inherited from interface org.eclipse.jetty.util.component.Container
getCachedBeans, getEventListenersMethods inherited from interface org.eclipse.jetty.util.component.Dumpable.DumpableContainer
isDumpable
-
Constructor Details
-
ContainerLifeCycle
public ContainerLifeCycle()
-
-
Method Details
-
doStart
Starts the managed lifecycle beans in the order they were added.- Overrides:
doStartin classAbstractLifeCycle- Throws:
AbstractLifeCycle.StopException- If thrown, the lifecycle will immediately be stopped.Exception- If there was a problem starting. Will cause a transition to FAILED state
-
start
Starts the given lifecycle.- Parameters:
l- the lifecycle to start- Throws:
Exception- if unable to start lifecycle
-
stop
Stops the given lifecycle.- Parameters:
l- the lifecycle to stop- Throws:
Exception- if unable to stop the lifecycle
-
doStop
Stops the managed lifecycle beans in the reverse order they were added.- Overrides:
doStopin classAbstractLifeCycle- Throws:
Exception- If there was a problem stopping. Will cause a transition to FAILED state
-
destroy
public void destroy()Destroys the managed Destroyable beans in the reverse order they were added.- Specified by:
destroyin interfaceDestroyable
-
contains
- Parameters:
bean- the bean to test- Returns:
- whether this aggregate contains the bean
-
isManaged
Description copied from interface:ContainerTest if this container manages a bean -
isAuto
- Parameters:
bean- the bean to test- Returns:
- whether this aggregate contains the bean in auto state
-
isUnmanaged
- Parameters:
bean- the bean to test- Returns:
- whether this aggregate contains the bean in auto state
-
addBean
Adds the given bean, detecting whether to manage it or not. If the bean is aLifeCycle, then it will be managed if it is not already started and not managed if it is already started. TheaddBean(Object, boolean)method should be used if this is not correct, or themanage(Object)andunmanage(Object)methods may be used after an add to change the status. -
addBean
Adds the given bean, explicitly managing it or not. -
addManaged
Adds a managed lifecycle.This is a convenience method that uses addBean(lifecycle,true) and then ensures that the added bean is started iff this container is running. Exception from nested calls to start are caught and wrapped as RuntimeExceptions
- Parameters:
lifecycle- the managed lifecycle to add
-
addEventListener
Description copied from interface:ContainerAdd an event listener. EventListeners added by this method are also added as beans.- Specified by:
addEventListenerin interfaceContainer- Specified by:
addEventListenerin interfaceLifeCycle- Overrides:
addEventListenerin classAbstractLifeCycle- Parameters:
listener- the listener to add- Returns:
- true if the listener was added
- See Also:
-
removeEventListener
Description copied from interface:ContainerRemove an event listener.- Specified by:
removeEventListenerin interfaceContainer- Specified by:
removeEventListenerin interfaceLifeCycle- Overrides:
removeEventListenerin classAbstractLifeCycle- Parameters:
listener- the listener to remove- Returns:
- true if the listener was removed
- See Also:
-
manage
Manages a bean already contained by this aggregate, so that it is started/stopped/destroyed with this aggregate. -
unmanage
Unmanages a bean already contained by this aggregate, so that it is not started/stopped/destroyed with this aggregate. -
setBeans
-
getBeans
-
getBeans
-
getBean
-
removeBeans
public void removeBeans()Removes all bean -
removeBean
Description copied from interface:ContainerRemoves the given bean. If the bean is-aEventListener, then also do an implicitContainer.removeEventListener(EventListener).- Specified by:
removeBeanin interfaceContainer- Parameters:
o- the bean to remove- Returns:
- whether the bean was removed
-
dumpStdErr
Dumps toSystem.err.- See Also:
-
dump
-
dump
Description copied from interface:DumpableDump this object (and children) into an Appendable using the provided indent after any new lines. The indent should not be applied to the first object dumped.- Specified by:
dumpin interfaceDumpable- Parameters:
out- The appendable to dump toindent- The indent to apply after any new lines.- Throws:
IOException- if unable to write to Appendable
-
dump
Dump this object to an Appendable with no indent.- Parameters:
out- The appendable to dump to.- Throws:
IOException- May be thrown by the Appendable
-
dumpObjects
Dump this object, it's contained beans and additional items to an Appendable- Parameters:
out- The appendable to dump toindent- The indent to apply after any new linesitems- Additional items to be dumped as contained.- Throws:
IOException- May be thrown by the Appendable
-
updateBean
-
updateBean
-
updateBeans
-
updateBeans
-
getContainedBeans
- Specified by:
getContainedBeansin interfaceContainer- Type Parameters:
T- the Bean type- Parameters:
clazz- the class of the beans- Returns:
- the list of beans of the given class from the entire Container hierarchy. The order is by depth first and then the order beans were added.
-
getContainedBeans
-