Return-Path: 
 <tapestry-dev-return-2239-apmail-jakarta-tapestry-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tapestry-dev-archive@www.apache.org
Received: (qmail 33916 invoked from network); 19 Dec 2003 03:23:40 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 19 Dec 2003 03:23:40 -0000
Received: (qmail 2786 invoked by uid 500); 19 Dec 2003 03:23:22 -0000
Delivered-To: apmail-jakarta-tapestry-dev-archive@jakarta.apache.org
Received: (qmail 2770 invoked by uid 500); 19 Dec 2003 03:23:21 -0000
Mailing-List: contact tapestry-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tapestry-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tapestry-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:tapestry-dev-help@jakarta.apache.org>
List-Post: <mailto:tapestry-dev@jakarta.apache.org>
List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org>
Reply-To: "Tapestry development" <tapestry-dev@jakarta.apache.org>
Delivered-To: mailing list tapestry-dev@jakarta.apache.org
Received: (qmail 2757 invoked from network); 19 Dec 2003 03:23:21 -0000
Received: from unknown (HELO rwcrmhc13.comcast.net) (204.127.198.39)
  by daedalus.apache.org with SMTP; 19 Dec 2003 03:23:21 -0000
Received: from almightybeast
 (h0010b50ed00a.ne.client2.attbi.com[24.128.112.68])
          by comcast.net (rwcrmhc13) with SMTP
          id <2003121903233001500r6h0he>
          (Authid: hlship);
          Fri, 19 Dec 2003 03:23:31 +0000
From: "Howard M. Lewis Ship" <hlship@comcast.net>
To: "'Tapestry development'" <tapestry-dev@jakarta.apache.org>
Subject: RE: is info level logging appropriate now?
Date: Thu, 18 Dec 2003 22:22:52 -0500
Message-ID: <01c701c3c5df$63b7bab0$6501a8c0@ALMIGHTYBEAST>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <014501c3c5d7$079f8080$0b01a8c0@silver>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

At one time I was very proud of all the logging Tapestry did ... but now I have better debuggers to
use :-)

I, for one, would not object to moving all of those life cycle output down from info to debug.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com

> -----Original Message-----
> From: Richard Lewis-Shell [mailto:rlewisshell@mac.com] 
> Sent: Thursday, December 18, 2003 9:23 PM
> To: tapestry-dev@jakarta.apache.org
> Subject: is info level logging appropriate now?
> 
> 
> i am trying to figure out why websphere is insisting on 
> logging tapestry 3's
> info messages on its console.  websphere appears to configure
> commons-logging to route log messages through its own logging package
> (JRas), so i looked into commons-logging.  this from commons-logging
> documentation 
> (http://jakarta.apache.org/commons/logging/use> rguide.html):
> 
> 
> General - Message Priorities/Levels
> <snip>
> 
> info - Interesting runtime events (startup/shutdown). Expect 
> these to be
> immediately visible on a console, so be conservative and keep 
> to a minimum
> </snip>
> 
> so now it seems reasonable for websphere to show tapestry's LOG.info()
> messages on the console.  what seems less reasonable is that 
> tapestry is
> using info for events that are not (imo) interesting - such 
> as a service
> start/end (AbstractEngine:850,996), adaptor registry loading
> (AdaptorRegistry:160), page loading (PageLoader:882) etc...
> 
> any thoughts?  (if not, i will change at least these messages 
> to debug)
> 
> it seems that there is actually a mismatch between commons-logging and
> log4j.  commons-logging has a level beneath debug: trace.  
> perhaps tapestry
> would be better off if all the messages were shunted down a level. ie.
> info -> debug, debug -> trace.  trace messages end up with 
> log4j as debug
> priority.  this will mean those using log4j will get them all on debug
> priority which seems unfortunate, but it appears to better match
> commons-logging (and thus non log4j logging impls, including JDK 1.4
> logging, and JRas).  any further thoughts?
> 
> R
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org