> since my project requires a functionality which
>can stop the parsing , and after sometime start it again from the same
>location.
The SAX APIs aren't designed to do that. The usual solution is to use
mulitasking -- run the parser in a thread, and set up the SAX handlers so
they only return when you want more data.
The other solution, if Xerces-C has the same "demand parsing" mechanism
that Xerces-J does, is to use those rather than the basic SAX parse-it-all
request. But of course that's relatively nonportble.
For a Java encapsulations of this mechanism, see the CoroutineParser.java
and CoroutineParser_Xerces.java classes recently added to the Xalan-J
package. That code could use a bit more cleanup, but it demonstrates one
way to safely "throttle" a SAX stream.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
