For concerns about Tracing/Logging I suggest take a look at:
http://www.log4j.org./
Josep Vela [EMAIL PROTECTED]
RD Manager
FIHOCA
Avda. Roma, 25
08029 Barcelona (Spain)
--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
snip
That this code does not belong to Jetspeed but to the framework. ;)
There are already way too many logging class around here and I don't
see the point in implementing yet another one.
Logging and debug features
For concerns about Tracing/Logging I suggest take a look at:
http://www.log4j.org./
Josep Vela [EMAIL PROTECTED]
RD Manager
FIHOCA
Avda. Roma, 25
8029 Barcelona (Spain)
Thanks for the hint, the API looks quite good, it has the required
isEnabledFor(Priority), isInfoEnabled() and
For concerns about Tracing/Logging I suggest take a look at:
http://www.log4j.org./
Josep Vela [EMAIL PROTECTED]
RD Manager
FIHOCA
Avda. Roma, 25
8029 Barcelona (Spain)
Thanks for the hint, the API looks quite good, it has the required
isEnabledFor(Priority), isInfoEnabled()
For a look at another good Logger implementation see:
http://protomatter.sourceforge.net/1.1.2/javadoc/com/protomatter/syslog/pack
age-summary.html
I'm no suggesting you use it, but you may get some useful ideas from the
organization of their API.
-Vik
--
on 1/9/2001 9:11 AM, "Victor Ganora" [EMAIL PROTECTED] wrote:
For a look at another good Logger implementation see:
http://protomatter.sourceforge.net/1.1.2/javadoc/com/protomatter/syslog/pack
age-summary.html
I'm no suggesting you use it, but you may get some useful ideas from the
[EMAIL PROTECTED] escribi:
Alan McAuley wrote:
// creates new String objects only if Log is logging
if (Log.isLogging()) {
Log.note("SimpleTransform: transforming url: " + url +
" with stylesheet: " + stylesheet_url );
}
What about centralising the
If you want to disable debugging for performance reason, you don't want to generate
the debug string because String manipulation is expensive in Java, so it makes
sense from a performance point of view to use the construct Thomas proposed
rather than filtering at the Log class level.
Alan McAuley wrote:
// creates new String objects only if Log is logging
if (Log.isLogging()) {
Log.note("SimpleTransform: transforming url: " + url +
" with stylesheet: " + stylesheet_url );
}
What about centralising the "isLogging" code to the Log class itself.
Santiago Gala wrote:
[EMAIL PROTECTED] escribi:
Alan McAuley wrote:
// creates new String objects only if Log is logging
if (Log.isLogging()) {
Log.note("SimpleTransform: transforming url: " + url +
" with stylesheet: " + stylesheet_url );
}
Raphael Luta wrote:
That this code does not belong to Jetspeed but to the framework. ;)
There are already way too many logging class around here and I don't
see the point in implementing yet another one.
Logging and debug features are important but should be (and maybe
are already )
11 matches
Mail list logo
