> As "the guy who receives all logged errors as email" in my "day job" project, > I must point out that you're wrong in your assumption; "... the process dies > ..." is simply wrong in our case
Glad to hear that but I stand by my words: Logging in Java is over-used and one reason for that is Java's checked exception handling. That has been my experience. > Considering logging to a DB, I’m kind of ambivalent. The “unspecified text > format” is a pita (I’m also “the guy that has to grep errors in the logs”). > But we log exclusively to local drives. Well any kind of embeded DB will use local drives too. It's not a secret I'm a fan of SQLite. It doesn't really matter though. A library can expose a hook that is called when something goes wrong and this hook is usually a callback with typed arguments (structured data). Whereas if you pass a logger instead the API will pass unstructured text to the logger you can provide. A worse design.
