org.apache.xalan.xslt.Process -VALIDATE (was: "Xalan phone home" from xalan-j-users)

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

Wow, I would never guess... Then something is wrong with it. The facts are:

1. "org.apache.xalan.xslt.Process" from Xalan 2.3.1 does not mention it
among available options if being run without arguments.

2. The line
    // System.out.println(resbundle.getString("optionVALIDATE")); //"
[-VALIDATE (Set whether validation occurs.  Validation is off by
default.)]");
   is commented out in the "org.apache.xalan.xslt.Process" source (line
#158).

3. The block for -VALIDATE option processing is also commented out (lines
#423-438)

4. The "org.apache.xalan.xslt.Process" behavior convinces that validation is
_on_ by default.

I believe we really need it as an available option. Otherwise any offline
processing of documents compliant with public definitions will fail (and it
in fact does - if i instruct my firewall to deny http calls from java to
w3c, Xalan dies with an error message).

Regards,
Sergey




----- Original Message -----
From: "Joseph Kesselman/CAM/Lotus" <jo...@us.ibm.com>
To: "Ushakov, Sergey N" <us...@int.com.ru>
Cc: <xa...@xml.apache.org>
Sent: Wednesday, May 01, 2002 2:53 AM
Subject: Re: Xalan phone home


>
> On Wednesday, 05/01/2002 at 02:42 ZE4, "Ushakov, Sergey N"
> <us...@int.com.ru> wrote:
> > Yes, that is. Xalan never "calls home" if there is no DTD/schema
> reference
> > in the doc.
>
> Gack. Sounds like something Xerces is doing. See if we can reproduce the
> problem with one of their test programs?
>
> > BTW, wouldn't it be wise to add a validation option to the command line
> > options list for "org.apache.xalan.xslt.Process" ?
>
> You mean like -VALIDATE, already present? (I'm not sure we're always
> honoring that switch, though...)
>
>
>