Hi Berin,
looking at the logger initialization code I noticed, that you set now
the default logger always to "" without any possibility to configure
a general root for all logger entries in your app. Since my web app
is already running in a logger hierarchy of the webserver, I would like to append my loogers into this it. Therefore I need the possibility to set it.
Currently I have 4 possibilities to config the base categories: - default logger ("" fix, unconfigurable) - logger of application (fortress by default) - logger attribute of roles (system.roles by default) - logger attribute of logkit (system.logkit by default) Unfortunately this leeds to log entries for the empty default logger I cannot influence at all.
If I set the default logger to XXX (by patching the code), the categories are as follows:
- default logger is now "XXX"
- logger of application is now "XXX.fortress"
- logger of roles is now "XXX.system.roles"
- logger of logkit is now "system.logkit"
All entries for the empty category are now part of category XXX. Fine.
So, do you mind if I send a patch modifying this to set the default logger to logger of application (fortress by default)? I would also set the default for logkit to XXX.system.logkit, too.
Go ahead.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
