Andy Clark wrote:
> David Walend wrote:
> > Once Xerces starts a parse, can it be stopped? How?
>
> Throw a SAXException from your registered handler.
Late last night, I decided to throw a subclass of SAXException named
SAXInterruptedException. (I've been assuming SAXExceptions were
relatively disasterous. I catch the subclass first, and ignore it; it's
not an error, just an interrupt.)
Still, it cuts accross a few methods, when it should go in one spot.
> Alternatively, if you want to drive the parser yourself,
> it can operate in pull-parser mode. In that way, you're
> only parsing as much as you need anyway.
That sounds promissing. Can you send me a pointer to something to read
on this?
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
