Re: Dynamically switching to/from a DOM ContentHandler during a SAX2 parse

At 11.44 17/11/2004 -0800, Pete Hodgson wrote: [..] Does anyone have any advice, or references to any relevent documentation? What you're describing sounds like what SAX calls "filtering": http://www.saxproject.org/?selected=filters From what I can see, Xerces-c doesn't implement the org.xml.sax.XM

Re: Dynamically switching to/from a DOM ContentHandler during a SAX2 parse

[EMAIL PROTECTED] wrote: I've been experimenting with using SAX2XMLReader::getSrcOffset() to find the file position that elements were found at. The problem with getSrcOffset() is that it doesn't always correspond exactly to the absolute file position, as (for example) XMLReader will sometimes sile

Re: Dynamically switching to/from a DOM ContentHandler during a SAX2 parse

[EMAIL PROTECTED] wrote on 11/17/2004 11:44:42 AM: > > So, my new question is, what would be involved in dynamically > > switching the ContentHandler attached to a SAX2 parser, so that > > some portions of a document could be parsed into a DOM document, > > and others handled by a custom implemen

Re: Dynamically switching to/from a DOM ContentHandler during a SAX2 parse

> I've been experimenting with using SAX2XMLReader::getSrcOffset() > to find the file position that elements were found at. The problem > with getSrcOffset() is that it doesn't always correspond exactly > to the absolute file position, as (for example) XMLReader will > sometimes silently eat the LF

Dynamically switching to/from a DOM ContentHandler during a SAX2 parse

Hi all, This is a follow up question from my original post below about accessing file position information during a SAX2 parse. I've been experimenting with using SAX2XMLReader::getSrcOffset() to find the file position that elements were found at. The problem with getSrcOffset() is that it does