On Mon, Sep 26, 2022 at 5:09 AM Thorsten Schöning <tschoen...@am-soft.de> wrote: > > * Having better error reporting - many exceptions that are thrown are > > basically swallowed and just print out to stderr at the moment. Come > > to think of it, do we even want exceptions? It seems like a bad idea > > for the logging framework to throw exceptions > > What else do you have in mind, some error handlers and callbacks? > Throwing and swallowing at some point doesn't sound that bad, as long > as the problem is visible somewhere. Logback pretty mich logs on > STDERR or STDOUT only as well. >
Yes, error handling and/or callbacks to notify the user. There are certain situations where there isn't much useful information available unless you're looking at STDERR, and even sometimes that information is pretty useless. For example, if you try to use the DOMConfigurator and the file isn't found, the only way for you to tell that something went wrong is to view the output of the process; this should probably return a bool or something to indicate that the configuration was successful or not. And then there's the incredibly unhelpful error message of "please initialize the log4cxx system properly" which should probably print out a bit more as to what it tried to do and why it failed. -Robert Middleton
