Re: Non-validating parse causes presence of the DTD to be checked?

["David H. Cook" <dc...@smartlynx.com>]

Thanks, Luke Blanshard and Jim Shane, for
the quick response and lucid explanations.

I guess we'll have to change our server to NOT include the
DTD reference in its XML stream.  (No doubt our older C++
clients are using XML-parsers that can deal with the
embedded DTD reference when doing their non-validating
parsing.)  I'm the developer charged with writing our
first Java-based client, and with your help, I now have
the facts I needed to resolve this issue in our code.

Thanks again and regards...

				Dave

Re: Non-validating parse causes presence of the DTD to be checked?

[Eric Ye <er...@locus.apache.org>]

There is another workaround suggested by Andy Clark a while ago, if all your
DTDs are referenced as external files:

implementing your own EntityResolver, whenever the resolver sees a external
DTD system id, replace it with some local copy of empty DTD file.

_____


Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org

----- Original Message -----
From: "David H. Cook" <dc...@smartlynx.com>
To: <xe...@xml.apache.org>
Sent: Thursday, November 30, 2000 5:10 PM
Subject: Re: Non-validating parse causes presence of the DTD to be checked?


> Thanks, Luke Blanshard and Jim Shane, for
> the quick response and lucid explanations.
>
> I guess we'll have to change our server to NOT include the
> DTD reference in its XML stream.  (No doubt our older C++
> clients are using XML-parsers that can deal with the
> embedded DTD reference when doing their non-validating
> parsing.)  I'm the developer charged with writing our
> first Java-based client, and with your help, I now have
> the facts I needed to resolve this issue in our code.
>
> Thanks again and regards...
>
> Dave
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>