You can get two different contexts from the ContextManager: the container context (m_childContext) and the container manager context (m_containerManagerContext)
You can get two different contexts from the ContextManager: the child context and the impl manager context. The former contains all managers, such as the pool manager etc. necessary for a child impl to create additional child containers. The impl manager context contains all of the child context, but also initialization parameters for the impl, such as a Configuration object, a ComponentLocator, etc., that the impl wants, but does not want to pass on to its children.
The container manager context is used to provide the container manager with all the data needed to initialize the container.
The container context is passed directly to the container.
The ContextManager will sometimes create new components, such as a service manager, a pool manager, etc. It will manage these components and dispose of them properly when it itself is disposed .
@author Avalon Development Team @version CVS $Revision: 1.55 $ $Date: 2004/04/05 12:05:38 $ @since 4.1The first implementation of the context manager assumes there is only one thread to worry about and that the user(s) of the class only create one instance of ContextManager.
A context manager tracks the sets of defined and enabled contexts within the application. The manager sends notification events to listeners when these sets change. It is also possible to retrieve any given context with its identifier.
This class is not intended to be extended by clients.
@since 3.1
|
|
|
|
|
|
|
|
|
|
|
|