Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 71314 invoked by uid 500); 17 May 2003 19:22:31 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 71299 invoked from network); 17 May 2003 19:22:31 -0000 Received: from mailserver1.hrz.tu-darmstadt.de (130.83.126.41) by daedalus.apache.org with SMTP; 17 May 2003 19:22:31 -0000 Received: from paris (paris.dvs1.informatik.tu-darmstadt.de [130.83.27.43]) by mailserver1.hrz.tu-darmstadt.de (8.12.9/8.12.8) with ESMTP id h4HJKopS012842 for ; Sat, 17 May 2003 21:20:50 +0200 Received: from bremen.dvs1.informatik.tu-darmstadt.de (bremen [130.83.27.69]) by paris (Postfix) with ESMTP id EE663FF2C for ; Sat, 17 May 2003 21:20:49 +0200 (MET DST) Received: from haul by bremen.dvs1.informatik.tu-darmstadt.de with local (Exim 3.36 #1 (Debian)) id 19H7Ef-0000N8-00 for ; Sat, 17 May 2003 21:20:49 +0200 Date: Sat, 17 May 2003 21:20:49 +0200 To: cocoon-dev@xml.apache.org Subject: Re: [BUG] Wrong error messages in database modular actions. Message-ID: <20030517192049.GB27888@bremen.dvs1.informatik.tu-darmstadt.de> Reply-To: haul@informatik.tu-darmstadt.de References: <34031.10.0.0.5.1053191794.squirrel@ags01.agsoftware.dnsalias.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <34031.10.0.0.5.1053191794.squirrel@ags01.agsoftware.dnsalias.com> Organization: Databases and Distributed Systems Group, Darmstadt University of Technology User-Agent: Mutt/1.5.4i From: Christian Haul X-MailScanner: Found to be clean X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On 17.May.2003 -- 11:16 AM, Antonio Gallardo wrote: > Hi: > > I am using Modular Database actions. I also turned on all the > option in the configuration of all 3 Actions. When an > error occur it always attach this string: > > "Could not add record" > > to the raised error (generated by JBDC Driver) even when we are deleting > or updating a record. I believe that the error message does not reflect the real cause because it is placed in DatabaseAction rather than any of the sub classes. > The complete error String I got is: > > > org.apache.cocoon.ProcessingException: Could not add record: > java.sql.SQLException: ERROR: $2 referential integrity violation - key in > bancos still referenced from empleados > > > The string is located at: > > org.apache.cocoon.acting.modular.DatabaseAction.act(DatabaseAction.java:800) see ;-) > I think we dont need to attach any string, since the message returned by > the JDBC controler is clear. > > I the worst case we need to change the String to something like: > > "A Database error" or "Cannot process the requested SQL statement". Right, good suggestion. Will do that when I'm back tue/wed. Thanks for reporting. 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