[brailleblaster] Re: Log levels, mapping mismatch

  • From: "Michael Whapples" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "mwhapples@xxxxxxx" for DMARC)
  • To: brailleblaster@xxxxxxxxxxxxx
  • Date: Tue, 15 Jul 2014 18:11:33 +0100

The answer is yes, but the longer answer is how do we want to do that?
The log levels in liblouisutdml are based on log4j's levels. I know some people like log4j more than the java.util.logging package. However the java.util.logging package is part of the standard JRE whereas log4j is an external dependency.
I know also that many are going down the route of the logging abstraction APIs such as slf4j. I don't think there is a huge amount to be gained for BrailleBlaster by using slf4j, I think slf4j more comes into its own in a library as then it is more flexible to mix with the logging API used in other parts of the application.
If we want to stick with java.util.logging then supposedly you can define custom levels, which we could do for the ones used in liblouisutdml. Should not be too much work but I need to read up how to define a custom level. 

Michael Whapples
On 15/07/2014 18:04, Keith Creasy wrote:

I like the levels in LibLouisUTDML better. Can we just change the 
BrailleBlaster levels?

K


-----Original Message-----
From: brailleblaster-bounce@xxxxxxxxxxxxx 
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Whapples
Sent: Tuesday, July 15, 2014 1:02 PM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Log levels, mapping mismatch

Hello,
The liblouis/liblouisutdml logging API and the BrailleBlaster logger have 
different levels and so do not quite match up properly.

Here are the levels for liblouis/liblouisutdml: FATAL, ERROR, WARN, INFO and 
DEBUG. Here are the levels in BrailleBlaster: SEVERE, WARNING, INFO, 
CONFIGURATION, FINE, FINER and FINEST.

We only need to go from the liblouis/liblouisutdml levels to the BrailleBlaster 
ones, we do not need to go the other way.

In mapping these I felt may be i should make INFO and WARNING levels on both 
match each other. The issue then is that liblouis/liblouisutdml has an 
additional higher priority level.

I resolved this mismatch by mapping both FATAL and ERROR to SEVERE.

How do others feel? Should I have mapped ERROR to WARNING? Another option would 
to have not mapped INFO to INFO and WARN to WARNING and just mapped each at 
increasing levels (eg. FATAL-SEVERE, ERROR-WARNING, WARN-INFO, 
INFO-CONFIGURATION, DEBUG-FINE).

Michael Whapples

Other related posts:

  1. Home
  2. brailleblaster
  3. Archive
  4. 07-2014