Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of craigmcc@gmail.com designates
 64.233.162.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references;
        b=Fm1XEJ6IyHqNcG/NT0y1tW5UEnzu1pHOtqPKg57D0rNIdn55XEHObuYU1YD/QdQtDebwhTUIPfuMJ+vL3KRDis5Tm0WFFwR/dxNW5GUD1vJaZnjmG1+PAxMCjS3OZ4rq0WRLPA+R27yhWQ3UZHy1IMg4+LPYuChRyHnMtz/if1M=
Message-ID: <f8b39ace0512071730n5728c6b6v29cd49c45b77663f@mail.gmail.com>
Date: Wed, 7 Dec 2005 17:30:29 -0800
From: Craig McClanahan <craigmcc@apache.org>
Sender: craigmcc@gmail.com
To: Struts Developers List <dev@struts.apache.org>, husted@apache.org
Subject: Re: Logging in MailReader 1.3
In-Reply-To: <8b3ce3790512071459j58a17cd7n9513179f32aae1a7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_12071_4114623.1134005429560"
References: <8b3ce3790512071459j58a17cd7n9513179f32aae1a7@mail.gmail.com>

------=_Part_12071_4114623.1134005429560
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 12/7/05, Ted Husted <ted.husted@gmail.com> wrote:
>
> So, if I'm deploying Tomcat 5.5. and compiling MailReader under Java
> 1.5, what do I need to do to adjust the logging level past "INFO".


I don't know the details of how Tomcat 5.5 is configured (and don't have it
on my laptop to check), but *if* you end up defaulting to the JDK logger,
there is a gotcha you need to pay attention to when you configure it.

This is done by editing $JDK_HOME/jre/lib/logging.properties and adding
lines like:

    org.apache.struts.level =3D 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 =3D INFO

as well, to whatever the most detailed level you want is.

Which begs the question: Do we still need so much logging in the
> MailReader? It's much easy to debug a web application in an IDE these
> days, and the logging statements tend to complicate the design. I
> wouldn't want to hedge on error handling (MailReader could actually
> use some more), but I don't know if the logging statements help or
> hinder at this point.
>
> To demonstrate logging, we could also do an example in the Cookbook
> application instead, and maybe show using different logging levels and
> such.


+1 on keeping logging in mailreader if it is *not* in the cookbook, +0 if i=
t
is.  I agree with you that logging should not lead you to scrimp on robust
error handling, but it's still a useful technique for the non-IDE user (as
Frank points out).  In addition, there's a whole different logging notion o=
f
tracking business transactions (instead of debugging messages) that we migh=
t
want to illustrate instead, either here and/or elsewhere.

Craig

-Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

------=_Part_12071_4114623.1134005429560--