 |
 |
 |
Hi,
You can stop the parser by throwing an
error. See more about it here:
http://www-128.ibm.com/developerworks/xml/library/x-tipsaxstop/
I guess restarting can be done if your
client remembers the namespaceURI, localName, qName, and attributes
and calls the startElement() method on the ContentHandler to pick up
from where you stopped. I didn't try it myself, but I think it should work.
Regards,
Radu Cernuta
2007/1/4, James Carr <james.r.carr@g...>:
Hi All,
I was curious if there are any implementations that enable pull sax
parsing? Basically, I want to be able to implement a sax parser where
I can specify it should halt processing if it reaches a certain point,
then pick back up on demand.
Currentlyu I've been playing with the XMLEventReader with stax, but
it'd be nice to find something simpler to use. ;)
Thanks,
James
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address:
http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe:
xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines:
http://www.oasis-open.org/maillists/guidelines.php
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |