Frank Schönheit - Sun Microsystems Germany wrote: > Hi Mathias, > >>> When we talk about seldom, hard to reproduce errors, then let's >>> introduce a logger which is permanently switched ON, or at least >>> switched ON for log levels >= LogLevel.SEVERE. (by default, loggers are >>> OFF, i.e. do not log any event, regardless of the LogLevel.) >> >> Everything that must be switched on doesn't help > > read again, please: ¨permanently switched on¨ was what I wrote :)
OK, that would be an option that could work. Logging errors until an error handler starts and perhaps creates an error report. But it works with exceptions and IMHO is the more natural approach. I agree with you that it's unfortunate not to have a "user compatible" way of handling and reporting errors. But we shouldn't clutch at straws and (mis)use something that comes close to that, we should find out what is the right way. User oriented error reporting in many (most?) cases can't be done by taking a message from the point where the exception occured, quite often it needs a context and perhaps even more. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[email protected]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
