dleslie     01/11/02 13:58:01

  Modified:    java/xdocs/sources/xalan readme.xml samples.xml
  Log:
  Information on new sample: ValidateXMLInput.
  
  Revision  Changes    Path
  1.60      +3 -0      xml-xalan/java/xdocs/sources/xalan/readme.xml
  
  Index: readme.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/readme.xml,v
  retrieving revision 1.59
  retrieving revision 1.60
  diff -u -r1.59 -r1.60
  --- readme.xml        2001/10/17 13:12:57     1.59
  +++ readme.xml        2001/11/02 21:58:01     1.60
  @@ -86,6 +86,9 @@
        <p>Beginning with this release, we are placing two distribution files in the 
<resource-ref idref="xslt4j-distdir"/>: a binary
        distribution file, which includes everything needed to run &xslt4j; and build 
applications, and a source distribution. For
        more information, see <link idref="getstarted" anchor="download">Downloading 
what you need</link>.</p>
  +     <p>This release also includes <link idref="samples" 
anchor="validatexmlinput">ValidateXMLInput</link>, a sample that illustrates 
  +     how you can verify that the XML input you are transforming adheres to its 
document type. It is in the samples/validate subdirectory
  +     along with a Validate utility that you can use to validate XML files without 
performing a transformation.</p>
        &done-j;
        </s3>
        <anchor name="other"/>
  
  
  
  1.40      +15 -0     xml-xalan/java/xdocs/sources/xalan/samples.xml
  
  Index: samples.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/samples.xml,v
  retrieving revision 1.39
  retrieving revision 1.40
  diff -u -r1.39 -r1.40
  --- samples.xml       2001/10/15 17:00:18     1.39
  +++ samples.xml       2001/11/02 21:58:01     1.40
  @@ -460,6 +460,20 @@
         Interface</link></p>
        </s2><anchor name="validate"/>
        <s2 title="Validate">
  +     <ul>
  +     <li><link anchor="validatexmlinput">ValidateXMLInput</link></li>
  +     <li><link anchor="validateutility">Validate utility</link></li>
  +     </ul><anchor name="validatexmlinput"/>
  +     <s3 title="ValidateXMLInput">
  +     <p>What it does: Uses <jump 
href="apidocs/javax/xml/parsers/SAXParserFactory.html">SAXParserFactory</jump> to turn 
on validation, and 
  +     <jump href="apidocs/org/xml/sax/XMLReader.html">XMLReader</jump> to parse the 
XML input and report errors and warnings to a SAX event
  +     handler. The XML input (birds.xml) contains an internal DOCTYPE declaration, 
and a few minor document type violations, which you are 
  +     invited to fix, add to, and vary in any way you find useful.</p>
  +     <p>Run this sample from the Validate subdirectory with</p>
  +     <p><code>java ValidateXMLInput</code></p>
  +     <note>This sample also shows you how to check validation without using an 
event handler to report validation errors.</note>
  +     </s3><anchor name="validateutility"/>
  +     <s3 title="Validate utility">
        <p>What it does: Uses the <jump 
href="apidocs\javax\xml\parsers\SAXParser.html">JAXP SAXParser</jump> with a SAX event 
handler 
        (extends <jump 
href="apidocs/org/xml/sax/helpers/DefaultHandler.html">DefaultHandler</jump> and 
implements 
        <jump 
href="apidocs/org/xml/sax/ext/LexicalHandler.html">LexicalHandler</jump>) to verify 
that XML files conform to their declared 
  @@ -472,6 +486,7 @@
        <note>A limitation: Files containing document parts appear to fail if you 
check them with Validate. Check readme.xml, 
        which "includes" by entity reference a number of files, and it passes. The 
parse operation scans the entire document
        with the includes. Check an "included" file (such as history.xml) as if it 
were an independent document and it fails.</note>
  +     </s3>
        </s2>
        <anchor name="trax"/>
        <s2 title="trax">
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to