Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 63940 invoked by uid 500); 21 Apr 2001 21:59:19 -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 63891 invoked from network); 21 Apr 2001 21:59:18 -0000 Message-ID: <000e01c0cab0$518af550$0100a8c0@flourish> From: "flourish" To: "cocoon" Subject: error handling schemes Date: Sat, 21 Apr 2001 18:13:38 -0400 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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N How are people handling errors in Cocoon? Up to now I've just had my logicsheets throw an error. I set handle.errors.internally to false when I'm in production and false when I'm developing. Then I created a general error page that apache displays to users on a 500 error. Ofcourse, this is just a quick and dirty fix. I already know I want to log errors to a file, and then show more information to the client through cocoon. I'm not sure what the best way to go about this is. Anyone have any general sudgestions or tips on error handling. Matt --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: