[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xml-dev] To continue parsing after a fatal error.
- From: Jeff Greif <firstname.lastname@example.org>
- To: Anoop A V <email@example.com>, firstname.lastname@example.org
- Date: Tue, 23 Oct 2001 12:35:14 -0700
Normally you might attempt to deal with this kind of problem using a custom
SAX error handler. In MSXML3, however, you may not be able to this, because
the underlying parsing code makes all errors fatal (calls the error
handler's fatalError ()method always, rather than ever calling its error()
or ignorableWarning() methods). It appears that treating all errors as fatal
limits recovery options.
Details (not very many) are here:
I only looked this up out of curiosity. I have not tried it myself and am
not pretending to be authoritative.
----- Original Message -----
From: "Anoop A V" <email@example.com>
Sent: Tuesday, October 23, 2001 10:51 AM
Subject: [xml-dev] To continue parsing after a fatal error.
> I have an 800 MB file which I need to parse. When I do this using MSXML
> parser, I get a fatal error with the message "Invalid character found in
> text content". And the parsing will be stopped. But I need to continue
> parsing the file even if an invalid character is met. I don't mind if that
> particular node(s) is skipped. But I need to parse the whole file. This
> is not under my control, so there is no question of my being able to edit
> this file and remove the invalid characters. Can anybody help?
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>