On 9 February 2012 22:21, Florian Semm <[email protected]> wrote: > but in my example the configuration was wrong and nothing went wrong. We're > wondering why the hell is our logger not writing anything in this log-file. > I have no good idea to solve the problem/case, without breaking the > inheritance.
Aha, I see what your objection is. Currently the configurator looks for the expected keys (such as 'appenders', 'rootLogger' and 'loggers') and validates their content. But unexpected keys (like 'productManagerLogger' in your example) are not processed, but simply ignored. It would not be too hard to add a check which triggers a warning if any unexpected keys are encountered. When writing the configurator I did try to make it report all possible configuration errors, and it is much better than it used to be. But this is still not handled. We can consider adding it for the next release. BTW, are you considering the invite? Regards, Ivan
