Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 95187 invoked by uid 500); 20 Nov 2002 16:34:06 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 95176 invoked from network); 20 Nov 2002 16:34:05 -0000 Message-ID: <3DDBB97F.5000800@informatik.tu-darmstadt.de> Date: Wed, 20 Nov 2002 17:34:07 +0100 From: Christian Haul User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913 Debian/1.1-1 X-Accept-Language: en-us, de MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Re: Two ESQL Questions References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Michael Edge wrote: > I have a couple of ESQL questions: > > 1) If an ESQL query throws a database exception, is there any way to log the stack trace to a file? Database exceptions are either rethrown as processing exceptions or handled by the code in esql:error-results This applies only for those errors that stem from the execute() method call i.e. setup-errors are different. > 2) If an ESQL query throws a database exception, is there any way to handle this using the section of the sitemap, so that all exceptions thrown, whether during pipeline processing or application exceptions, are displayed in the same manner? see above. Chris. -- C h r i s t i a n H a u l haul@informatik.tu-darmstadt.de fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: