Those catches outside of the parse() calls are just to catch something that
might go catastrophically wrong before the parsing can really get started.
Its very unlikely to happen, and in any particular release might not ever
happen. But you should be prepared to handle them if they do. If they do,
then something is likely to be very, very wrong and it should be taken
seriously. Otherwise, errors are reported via the error handler mechanism.
--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-----Original Message-----
From: Houle, Dennis W [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 2:31 PM
To: [EMAIL PROTECTED]
Subject: DOMPrint parser exception question
Team Xerces,
The ErrorHandler documentation states "The parser shall use this interface
instead of throwing an exception" and DOMTreeErrorReporter doesn't throw any
exception either.
So how does control ever get passed to the parser's catch block in DOMPrint?
Thanks for the additional info.
Dennis W. Houle
Tactical Communications Networks
The Boeing Company
(714) 762-0291
(714) 762-2253 (fax)
[EMAIL PROTECTED]
---------------------------------------------------------------------
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]
