Re: org.apache.xalan.xslt.Process -VALIDATE

["Ushakov, Sergey N" <us...@int.com.ru>]

Now i see it's not that simple. But i can suggest a very generic approach. A
general purpose class(es) might be written that would implement
EntityResolver (and maybe DTDHandler?) and resolve all requests by using a
local copy of DTD/schema. I wonder whether it is still not implemented...

Regards,
Sergey


----- Original Message -----
From: "Joseph Kesselman/CAM/Lotus" <jo...@us.ibm.com>
To: <xa...@xml.apache.org>
Sent: Wednesday, May 01, 2002 7:13 PM
Subject: Re: org.apache.xalan.xslt.Process -VALIDATE (was: "Xalan phone
home" from xalan-j-users)


>
> On Wednesday, 05/01/2002 at 10:28 EDT, Joseph Kesselman/CAM/Lotus wrote:
> > We should probably take this to xalan-dev only, since it's about
> enhancements
> > rather than usage of the current code.
>
> Actually, as my reply there pointed out, there _are_ things an ordinary
> user
> can do:
>
> 1) Install an EntityResolver that blocks the attempt to retrieve the DTD
> (which
> we'd have to do anyway to address this request, since simply turning off
> validation is insufficient -- DTDs are used for more than validation).
>
> 2) Or: Use the Xalan API to create your own front-end rather than using
> Process.java. Configure a parser the way you want it, wrap a SAXSource
> around
> that and pass it to Xalan.
>
>
>