I'm so ignorant. I fixed the problem earlier by implementing an ErrorHandler class, and to make sure the implementations actually threw the SAXExceptions. On top of not figuring this out, I forgot to include the relevant part of my code in which I configured the Digester object.
Oh well, I suppose I was frustrated at the time. Thanks for the response! On Sat, 03 Jul 2004 15:03:22 +1200, Simon Kitching <[EMAIL PROTECTED]> wrote: > > > On Sat, 2004-07-03 at 09:32, Dan Tarkenton wrote: > > Hello, I'm as confused as possible. I'm using Digester 1.5 binaries. > > > > > > Now, I intentionally try and break my TestResults.xml so that it will > > throw a SAXParseException. I'm trying to test for this case. Below > > is part of my log file: > > > > What gives here? It certainly is running into a SAXParseException, > > but it doesn't seem to be throwing it. I.e. i never get a > > TestResultsException. > > > > Do I need to configure something else? I looked at the API and I > > thought I had this set to validate against my DTD. I'm in desparate > > need of help! > > Hi Dan, > > You probably need to define a class which implements > org.xml.sax.ErrorHandler and pass an instance of your class to the > digester via > digester.setErrorHander(eh); > > Digester extends org.xml.sax.helpers.DefaultHandler, and the default > implementation it inherits from there is to completely ignore errors > reported during parsing. > > If you search the email archives, you should find some additional > information on this topic. > > Regards, > > Simon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
