RE: Stopping Saxon searching for an external DTD

> Answering my own question:
>
> I've read through the relevant bits of the Saxon and SAX source (not
> something someone with < 2 months Java experience should do - i've
> got a funny pain in my right eye now) and it turns out it's the way
> the SAX interface is implemented. SAX demands that Public/System IDs
> are resolved (but not downloaded) which obviosuly doesn't happen
> without a TCP/IP connection to DNS server. All I have to do is find
> out where it's called in Saxon and turn it off...

Your best bet is to supply the SAX parser with an EntityResolver that
returns a dummy local DTD in place of the remote one.

Note that DTD resolution is entirely the job of the XML parser, it has
nothing to do with the XSLT processor.

Mike Kay


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list