[logback-dev] [JIRA] Created: (LBCLASSIC-190) Allow programmatic traversal of the logger tree

[Robert Elliot (JIRA)]

Allow programmatic traversal of the logger tree
-----------------------------------------------

                 Key: LBCLASSIC-190
                 URL: http://jira.qos.ch/browse/LBCLASSIC-190
             Project: logback-classic
          Issue Type: Improvement
          Components: Other
    Affects Versions: 0.9.19
            Reporter: Robert Elliot
            Assignee: Logback dev list


I'm interested in writing a module for logback to allow on the fly changes to the logger tree - changing levels, adding appenders, maybe adding filters with code supplied dynamically. My vision for the gui is to show the logger tree like a folder tree.

However, now I come to look at it it seems neither the child loggers nor the parent logger of a logger are exposed, which rather blows this whole concept out of the water.

Is there a particularly strong reason for this?  If not, I've forked logback here:
http://github.com/Mahoney/logback
and exposed the data.  As part of the same thing I changed the children from a List to a Set as it seems more semantically correct and cleans up the code slightly.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira