Thread: [Jsdsi-devel] Logging framework
Status: Pre-Alpha
Brought to you by:
sajma
From: Sean R. <sra...@ae...> - 2004-06-10 09:11:53
|
Here's a question that I've been meaning to ask. How do people feel about logging frameworks? I myself think logging is a good idea as it is a great tool to track down problems in live systems. So I would like to ask how people feel to adding the apache commons-logging to jsdsi. The reason to go for that rather than straight for either log4j or java.util.logging is that it is an abstraction to other logging frameworks so the target environment can be using whatever it choses (or nothing). An example: most (all) J2EE application containers use log4j... If jsdsi uses JDK logging then ALL the messages appear at the ERROR level or are discarded completely! I think logging is becoming more and more needed in JSDSI, especially as it will become more complicated with more functionality in the future. Regards, Sean -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com |
From: Sameer A. <aj...@cs...> - 2004-06-10 14:14:10
|
Logging is always a good idea. In JSDSI, it would be very helpful to have logging in the prover and verifier. If most applications use log4j, why do you suggest apache commons-logging? Are they compatible? (they're both Apache team products, right?) Or do you mean we can just plug log4j into commons-logging, and other users can plug alternative logging frameworks into it? Sameer > Here's a question that I've been meaning to ask. > > How do people feel about logging frameworks? > > I myself think logging is a good idea as it is a great tool to track > down problems in live systems. So I would like to ask how people feel to > adding the apache commons-logging to jsdsi. The reason to go for that > rather than straight for either log4j or java.util.logging is that it is > an abstraction to other logging frameworks so the target environment can > be using whatever it choses (or nothing). > > An example: most (all) J2EE application containers use log4j... If jsdsi > uses JDK logging then ALL the messages appear at the ERROR level or are > discarded completely! > > I think logging is becoming more and more needed in JSDSI, especially as > it will become more complicated with more functionality in the future. > > Regards, > > Sean > > > -- > Dr. Sean Radford, MBBS, MSc > sra...@ae... > http://www.aegeus-technology.com > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: GNOME Foundation > Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. > GNOME Users and Developers European Conference, 28-30th June in Norway > http://2004/guadec.org > _______________________________________________ > Jsdsi-devel mailing list > Jsd...@li... > https://lists.sourceforge.net/lists/listinfo/jsdsi-devel http://ajmani.net |
From: Sean R. <sra...@ae...> - 2004-06-10 14:32:40
|
On Thu, 2004-06-10 at 15:14, Sameer Ajmani wrote: > Logging is always a good idea. In JSDSI, it would be very helpful to have > logging in the prover and verifier. > > If most applications use log4j, why do you suggest apache commons-logging? > Are they compatible? (they're both Apache team products, right?) Or do > you mean we can just plug log4j into commons-logging, and other users can > plug alternative logging frameworks into it? That's exactly it. commons-logging is an abstraction layer for logging that uses log4j, JDK logging, it's own simple logger, a dummy logger or whatever framework you care to connect it to. Sean > > Sameer > > > Here's a question that I've been meaning to ask. > > > > How do people feel about logging frameworks? > > > > I myself think logging is a good idea as it is a great tool to track > > down problems in live systems. So I would like to ask how people feel to > > adding the apache commons-logging to jsdsi. The reason to go for that > > rather than straight for either log4j or java.util.logging is that it is > > an abstraction to other logging frameworks so the target environment can > > be using whatever it choses (or nothing). > > > > An example: most (all) J2EE application containers use log4j... If jsdsi > > uses JDK logging then ALL the messages appear at the ERROR level or are > > discarded completely! > > > > I think logging is becoming more and more needed in JSDSI, especially as > > it will become more complicated with more functionality in the future. > > > > Regards, > > > > Sean > > > > > > -- > > Dr. Sean Radford, MBBS, MSc > > sra...@ae... > > http://www.aegeus-technology.com > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: GNOME Foundation > > Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. > > GNOME Users and Developers European Conference, 28-30th June in Norway > > http://2004/guadec.org > > _______________________________________________ > > Jsdsi-devel mailing list > > Jsd...@li... > > https://lists.sourceforge.net/lists/listinfo/jsdsi-devel > > > http://ajmani.net > -- Dr. Sean Radford, MBBS, MSc sra...@ae... http://www.aegeus-technology.com |