Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 48573 invoked from network); 20 Feb 2002 19:58:12 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 20 Feb 2002 19:58:12 -0000 Received: (qmail 5337 invoked by uid 97); 20 Feb 2002 19:57:18 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 5311 invoked by uid 97); 20 Feb 2002 19:57:18 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 5262 invoked from network); 20 Feb 2002 19:57:18 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Digester parsing user question Date: Wed, 20 Feb 2002 11:51:16 -0800 Message-ID: <458473676F1AC74A84EAB2F22004DA6D1B2127@mail.nextance.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Digester parsing user question Thread-Index: AcG6R4RBzkVIuKfnTEaDTOFee0Ie6wAAD1lQ From: "Scott Sanders" To: "Jakarta Commons Developers List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N As far as I know the code, all SAXExceptions are bubbled straight to the user (you), Digester 'swallows' nothing. Typically with a SAX parser, you get the first exception and then it fails. It is not like a compiler, which keeps reporting errors, so you should be able to catch the first and only exception that the parser spits out. Cheers, Scott Sanders > -----Original Message----- > From: Kyle Robinson [mailto:KRobinson@pangaeainc.com]=20 > Sent: Wednesday, February 20, 2002 11:58 AM > To: 'commons-dev@jakarta.apache.org' > Subject: Digester parsing user question >=20 >=20 > When I pass a badly formed xml document into my=20 > digester.parse() method it seems to be handling an=20 > SAXParseExceptions internally. How can I catch the=20 > SAXParseExceptions myself? (For example: I want to add the > exception.getMessage() to a Vector of Strings)=20 > =20 > Any help would be appreciated, thanks. > =20 > Kyle Robinson > Systems Consultant > Pangaea Systems Inc. > (250) 360-0111 > =20 >=20 -- To unsubscribe, e-mail: For additional commands, e-mail: