Manager provides operations for obtaining the contextual instance of the webbeans. There are operations related with; There is always one root manager in the system. You can set the current activity via call to the {@link Manager#setCurrent(Class)} method.
@version $Rev$ $Date$ In order for a Manager implementation to successfully operate with a Context implementation that implements reloading, it must obey the following constraints:
Lifecycle so that the Context can indicate that a restart is required. stop() to be followed by a call to start() on the same Manager instance. Sitemaps of a Sitemap Invokation of sub sitemaps will be done by this instance as well checking regeneration of the sub Sitemap
@author Giacomo Pati
@version CVS $Id: Manager.java,v 1.9 2002/02/22 07:03:55 cziegeler Exp $
Manager service can be used to programmatically register {@link org.apache.karaf.shell.api.action.Action}s or {@link org.apache.karaf.shell.api.console.Completer}s. Registered objects must be annotated with the {@link Service} annotation.Objects will be registered in the {@link org.apache.karaf.shell.api.console.Registry}associated with this Manager.
@see org.apache.karaf.shell.api.console.Registry
@see org.apache.karaf.shell.api.action.lifecycle.Service
Better documentation/diagrams coming, the best way to learn right now is to see how it is invoked in one of the message layer implementations.
The main documentation task is to document the tricky areas like 'legal inputs' etc. From looking at the method names you should be able to see the basic usage:
Click on the "Manager" link above to see the source code which has a more natural grouping of the methods.
todo: document each method independently
todo: richer exceptions/hiearchy
@author Felix Jost
| |
| |
| |