Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 20242 invoked by uid 500); 13 May 2002 14:22:44 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 20227 invoked from network); 13 May 2002 14:22:44 -0000 Subject: RE: logging question: catch (Exception) throw AxisFault To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Richard Sitze" Date: Mon, 13 May 2002 09:22:00 -0500 X-MIMETrack: Serialize by Router on D04NM201/04/M/IBM(Release 5.0.9a |January 7, 2002) at 05/13/2002 10:22:38 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N If exceptions are in fact exceptional (rare), then is (1) really an issue? ******************************************* Richard A. Sitze rsitze@us.ibm.com CORBA Interoperability & WebServices IBM WebSphere Development Glyn Normington/UK/IB To: axis-dev@xml.apache.org M@IBMGB cc: Subject: RE: logging question: catch (Exception) throw AxisFault 05/13/2002 03:38 AM Please respond to axis-dev Two valid requirements have been mentioned and need to be reconciled: 1. The need to avoid flooding the console log with debug-related messages. 2. The need to avoid losing potentially critical debugging information when an exception occurs (especially if the exception is not wrapped and re-thrown). One way to reconcile them is to send debug information (stack trace etc.) to a separate log (which could reside by default in a file) so that just the occurrence of a failure need be indicated on the console log. Glyn