[rfc][icedtea-web] refactored logging

Omair Majid omajid at redhat.com
Fri Sep 13 11:06:53 PDT 2013


On 09/13/2013 10:18 AM, Jiri Vanek wrote:
> On 09/12/2013 07:09 PM, Omair Majid wrote:
>> Are those exceptions worth logging? (or even worth stopping and showing
>> an error to the user?)
> Well thats the question. Which exception/message is which? There was
> nearly thousand of substitutions...  Can you imagine to evaluate each one?

I suspect we will have to. Most of these are really-for-debugging
messages. Some of they may be interesting to users, but most of them
probably will not be.

Otherwise we are syslog()ing all those (not-so-helpful) messages.

> Anyway  - four orriginally logged messages was nearly not worthy tobe
> logged.... Then the Logger was moreover forgotten :(

Sorry, I am not clear about this. Can you elaborate?

> TBH - personally I dont like java logging api - it is clumsy, and
> actually not helping at all.  Also I found it not suiting to ITW.

Can you elaborate some more on this? What is it about the logging API
that you think is not helping? I am only asking so I don't
(accidentally) suggest repeating the issues.

I am also a little confused. The only place that uses java.util.logging
is Log (and AppletLog). As a complete aside, what are those 2 classes
doing? Are they just used in one place (showAppletExceptions)?

> It loosk like wee need to solve the system level implementation asap,
> otherwise some of mentioned questions cannot be answered correctly.

I think that's a good idea. If we are making a change because it helps a
future change, let's try and narrow down exactly what that future change is.

PGP Key: 66484681 (http://pgp.mit.edu/)
Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681

More information about the distro-pkg-dev mailing list