This class is specialized in retrieving loggers by name and also maintaining the logger hierarchy.
The casual user does not have to deal with this class directly.
The structure of the logger hierarchy is maintained by the getLogger method. The hierarchy is such that children link to their parent but parents do not have any pointers to their children. Moreover, loggers can be instantiated in any order, in particular descendant before ancestor.
In case a descendant is created before a particular ancestor, then it creates a provision node for the ancestor and adds itself to the provision node. Other descendants of the same ancestor add themselves to the previously created provision node.
Located in /LoggerHierarchy.php (line 46)
Create a new logger hierarchy.
Add a HierarchyEventListener event to the repository.
Not Yet Impl.
Add an object renderer for a specific class.
This call will clear all logger definitions from the internal hashtable.
Check if the named logger exists in the hierarchy.
Returns all the currently defined categories in this hierarchy as an array.
Return a new logger instance named as the first parameter using the default factory.
Return a new logger instance named as the first parameter using the default factory.
This method will return true if this repository is disabled for level object passed as parameter and false otherwise.
Reset all values contained in this hierarchy instance to their default.
This removes all appenders from all categories, sets the level of all non-root categories to null, sets their additivity flag to true and sets the level of the root logger to LOGGER_LEVEL_DEBUG. Moreover, message disabling is set its default "off" value.
<p>Existing categories are not removed. They are just reset.
<p>This method should be used sparingly and with care as it will block all logging until it is completed.</p>
Used by subclasses to add a renderer to the hierarchy passed as parameter.
Shutting down a hierarchy will safely close and remove all appenders in all categories including the root logger.
Some appenders such as LoggerSocketAppender need to be closed before the application exists. Otherwise, pending logging events might be lost.
The shutdown method is careful to close nested appenders before closing regular appenders. This is allows configurations where a regular appender is attached to a logger and again to a nested appender.
Documentation generated by phpDocumentor 1.3.2