Rename AggregateLifeCycle to ContainerLifeCycle in javadoc
This commit is contained in:
parent
accc3b321a
commit
0c84eefdcc
|
@ -31,9 +31,9 @@ import org.eclipse.jetty.util.log.Log;
|
||||||
import org.eclipse.jetty.util.log.Logger;
|
import org.eclipse.jetty.util.log.Logger;
|
||||||
|
|
||||||
/**
|
/**
|
||||||
* An AggregateLifeCycle is an {@link LifeCycle} implementation for a collection of contained beans.
|
* An ContainerLifeCycle is an {@link LifeCycle} implementation for a collection of contained beans.
|
||||||
* <p>
|
* <p>
|
||||||
* Beans can be added the AggregateLifeCycle either as managed beans or as unmanaged beans. A managed bean is started, stopped and destroyed with the aggregate.
|
* Beans can be added 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 {@link #dump()}, but it's lifecycle must be managed externally.
|
* An unmanaged bean is associated with the aggregate for the purposes of {@link #dump()}, but it's lifecycle must be managed externally.
|
||||||
* <p>
|
* <p>
|
||||||
* When a {@link LifeCycle} bean is added with out a managed state being specified, if it is already started, then it is assumed to be an unmanaged bean.
|
* When a {@link LifeCycle} bean is added with out a managed state being specified, if it is already started, then it is assumed to be an unmanaged bean.
|
||||||
|
|
Loading…
Reference in New Issue