|
Default initialization of log4net: msg#00059log.log4net.user
Hi, recently i realized that there was some logging output via log4net in my app before any initialization by one of the configurators happened. This logging calls lead to no output on any of the logging sinks at all and I started wondering how log4net handles these calls internally. As I could not find any documentation on this for log4net, I found out that log4j features a default initialization procedure that is called in any case before a logging call can be written to the log4j framework.This default initialization can be configured a log4j.xml or an log4j.properties file. In addition, I do not get any compiler warnings using log4net whereas the log4j documentation explicitly mentions them if no configuration happened and a logging call happens. Any ideas? Regards, Alex |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: NDC in threads?: 00059, Oliver Sturm |
|---|---|
| Next by Date: | Stability of log4net: 00059, Steve Slatcher |
| Previous by Thread: | Programmatically determine if DOMConfigurator.Configure() failedi: 00059, Thibaut Barrère |
| Next by Thread: | RE: Default initialization of log4net: 00059, Nicko Cadell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |