Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 48264 invoked from network); 5 Jul 2000 01:36:23 -0000 Received: from neon.kcs.com.au (HELO neon.whitewolf.com.au) (203.14.58.64) by locus.apache.org with SMTP; 5 Jul 2000 01:36:23 -0000 Received: (qmail 18491 invoked by alias); 5 Jul 2000 01:39:26 -0000 Received: from unknown (HELO oxygen.kcs.com.au) (10.14.58.23) by 10.14.58.64 with SMTP; 5 Jul 2000 01:39:26 -0000 Received: (qmail 28148 invoked from network); 5 Jul 2000 01:32:08 -0000 Received: from silicon.kcs.com.au (HELO silicon) (10.14.58.30) by oxygen.kcs.com.au with SMTP; 5 Jul 2000 01:32:08 -0000 Message-ID: <016901bfe620$9fd2fd90$1e3a0e0a@kcs.com.au> From: "Geoff Soutter" To: References: Subject: Re: Custom logs must die Date: Wed, 5 Jul 2000 11:30:38 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N note that the next release of the Java platform will likely include a logging api which has it's own XML format. So if I was you guys I'd ditch any custom XML formats altogether till that comes out of the JSR process cheers Geoff > On Tue, 4 Jul 2000, Alex Chaffee wrote: > > I agree that would be nice. However, right now, it doesn't do that; it > > just wraps the whole bloody message in a single tag that happens to be > > the same as the name of the log file you're in, e.g. > > timestamp - blah blah blah > > > > I'm suggesting we kill "custom" and then later maybe add an "xml" > > format, e.g. > > > > > > 2000-07-04 > > > > ContextManager > > something happened > > java.lang.NullPointerException > > ...stacktrace... > > > > > > > > but not yet! > > > > - A