On 12/7/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > This is done by editing > $JDK_HOME/jre/lib/logging.properties and adding lines like: > > org.apache.struts.level = FINEST > > to get trace-level debugging from every Struts class. However, there is an > additional uber-limit on the severities that go to the console log -- and > the default limits it to INFO. Change > > java.util.logging.ConsoleHandler.level = INFO > > as well, to whatever the most detailed level you want is.
Hmmm, there's a logging.properties file there, but adding the line didn't seem to help. For now, I'll just have to assume that I didn't break anything :) > In addition, there's a whole different logging > notion of tracking business transactions (instead of debugging messages) > that we might want to illustrate instead, either here and/or elsewhere. My own itch is to illustrate how we actually write our own applications. So, if business transactions is something we would log at work, then, yes, I'd suggest we log them in the MailReader. >From my own work, I believe, most often, teams log serious error conditions along with possible security exceptions, and sometimes might include optional statements to study throughput. I've done things like log IPs when users log in, in case I need to trace something back. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
