Damien Neil added the comment:
On Feb 3, 2009, at 3:12 PM, Martin v. Löwis wrote:
> This is DOM parsing, not SAX parsing.
1) The title of this ticket begins with "xml.sax and xml.dom...".
2) I am creating a SAX parser and passing it to xml.dom, which uses it.
> So break layer
Damien Neil added the comment:
I just discovered another really fun wrinkle in this.
Let's say I want to have my entity resolver return a reference to my
local copy of a DTD. I write:
source = xml.sax.InputSource()
source.setPublicId(publicId)
source.setSystemId(sys
Damien Neil added the comment:
On Feb 3, 2009, at 1:42 PM, Martin v. Löwis wrote:
> Sure. But ContentHandler.setDocumentLocator receives it, and you are
> supposed to store it for the entire parse, to always know what entity
> is being processed if you want to.
Where in the following
Damien Neil added the comment:
On Feb 3, 2009, at 11:23 AM, Martin v. Löwis wrote:
> I don't think this is actually the case. Did you try calling getSystemId
> on the locator?
EntityResolver.resolveEntity() is called with the publicId and systemId as
arguments. It does not receiv
Damien Neil added the comment:
I just ran into this problem. I was very surprised to realize that
every time the code I was working on parsed a docbook file, it generated
several HTTP requests to oasis-open.org to fetch the docbook DTDs.
I attempted to fix the issue by adding an
