You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by an...@locus.apache.org on 2000/01/28 23:57:25 UTC
cvs commit: xml-xerces/java/docs api.xml docs-book.xml entities.ent faq-build.xml faq-general.xml faq-migrate.xml faq-write.xml feedback.xml install.xml readme.xml sam-iterator.xml samples.xml schema.xml
andyc 00/01/28 14:57:25
Modified: java/docs api.xml docs-book.xml entities.ent faq-build.xml
faq-general.xml faq-migrate.xml faq-write.xml
feedback.xml install.xml readme.xml
sam-iterator.xml samples.xml schema.xml
Log:
Updating docs.
Revision Changes Path
1.4 +1 -1 xml-xerces/java/docs/api.xml
Index: api.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/api.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- api.xml 1999/12/29 01:07:43 1.3
+++ api.xml 2000/01/28 22:57:23 1.4
@@ -3,7 +3,7 @@
<s1 title="API Documentation">
<s2 title="Javadoc Generated Documentation">
- <p>&javaparsername; comes packaged with API documentation for SAX and DOM,
+ <p>&javaparsernamelong; comes packaged with API documentation for SAX and DOM,
the two most common interfaces for programming XML. In addition,
we provide documentation for classes that are not part of the SAX
and DOM API's, but are useful for writing &javaparsername; programs. </p>
1.3 +8 -2 xml-xerces/java/docs/docs-book.xml
Index: docs-book.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/docs-book.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- docs-book.xml 2000/01/25 00:06:24 1.2
+++ docs-book.xml 2000/01/28 22:57:23 1.3
@@ -11,8 +11,12 @@
<separator/>
<document id="api" label="API Docs" source="api.xml" />
<document id="samples" label="Samples" source="samples.xml" />
- <hidden id="iterator" source="sam-iterator.xml"/>
- <hidden id="tree" source="sam-tree.xml" />
+ <hidden id="domcount" source="sam-domcount.xml"/>
+ <hidden id="domwriter" source="sam-domwriter.xml"/>
+ <hidden id="domfilter" source="sam-domfilter.xml"/>
+ <hidden id="iterator" source="sam-iterator.xml"/>
+ <hidden id="tree" source="sam-tree.xml" />
+ <hidden id="treeview" source="sam-treeview.xml" />
<document id="schema" label="Schema" source="schema.xml" />
<separator/>
@@ -22,9 +26,11 @@
<entry id="faq-general" source="faq-general.xml" />
<entry id="faq-build" source="faq-build.xml" />
<entry id="faq-write" source="faq-write.xml" />
+ <entry id="faq-performance" source="faq-performance.xml" />
<entry id="faq-migrate" source="faq-migrate.xml" />
<entry id="faq-common" source="faq-common.xml" />
</group>
+ <hidden id="jpc" source="javapurecheck.xml"/>
<separator/>
<document id="releases" label="Releases" source="releases.xml" />
1.3 +10 -4 xml-xerces/java/docs/entities.ent
Index: entities.ent
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/entities.ent,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- entities.ent 1999/12/20 17:41:02 1.2
+++ entities.ent 2000/01/28 22:57:23 1.3
@@ -1,5 +1,15 @@
<?xml encoding="US-ASCII"?>
+<!ENTITY javaparsernamelong "Xerces Java Parser">
+<!ENTITY javaparsername "Xerces-J">
+<!ENTITY javaparserversion "1.0.2">
+<!ENTITY javaparserdirectory "xerces">
+<!ENTITY javaparserdistname "Xerces-J-bin"> <!-- name of binaries -->
+
+
+
+
+
<!ENTITY XercesCFullName "Xerces C++ Parser"> <!-- fullproductname -->
<!ENTITY XercesCName "Xerces-C"> <!-- productname -->
<!ENTITY XercesCVersion "1.0"> <!-- versionnumber -->
@@ -10,7 +20,3 @@
<!ENTITY XercesCUnixLib "libxerces-c1_0"> <!-- unixlibname -->
<!ENTITY XercesCEmailAddress "xerces-dev@xml.apache.org "> <!-- emailaddress -->
-<!ENTITY javaparsername "Xerces">
-<!ENTITY javaparserversion "1.0.1">
-<!ENTITY javaparserdirectory "xerces">
-<!ENTITY javaparserdistname "Xerces-J-bin"> <!-- name of binaries -->
1.4 +103 -31 xml-xerces/java/docs/faq-build.xml
Index: faq-build.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-build.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq-build.xml 2000/01/24 23:43:48 1.3
+++ faq-build.xml 2000/01/28 22:57:23 1.4
@@ -64,7 +64,7 @@
</li>
<li>Are there any other tips for importing the &javaparsername; parser into VisualAge
for Java 2.0?
- <br/>The most useful tip applies to *any* updated code that you import
+ <br/>The most useful tip applies to <em>any</em> updated code that you import
into the VisualAge for Java 2.0 product. Before updating code, do the following:
<br/>1. version the old code
<br/>2. delete it from your workspace
@@ -83,42 +83,114 @@
</faq>
<faq title="100% Pure Java compliant?">
<q>Is this &javaparsername; version 100% pure Java compliant?</q>
- <a> <p>tba
- </p>
+ <a> <p>Running JavaPureCheck on the Xerces-J parser code indicated 339
+ pure Java classes, 9 warnings, and 0 errors. The nine warnings are
+ enumerated below with explanations. To see the entire report, click
+ <link idref="jpc">here</link>. </p>
+
+ <p>There are many common cases where JavaPureCheck issues warnings
+ even though the code is pure Java. These are the most common reasons:</p>
+ <ol>
+ <li>Warning: method reference:
+ <code>java.lang.Class.forName(java.lang.String)</code>
+ <br/>This warning is issued in the following two cases:</li>
+ <ol>
+ <li>Program code calls the <code>Class.forName(String)</code> method to
+ dynamically load a class file. In this situation, the
+ specified class may contain impure Java code. In the
+ cases where this method is called directly in the parser
+ code, an explanation is provided detailing why this
+ warning can be ignored.</li>
+ <li>Program code makes direct reference to an object's
+ class. For example: <code>Class stringClass = String.class;</code>.
+ In this situation the Java compiler converts
+ <code>String.class</code> to the method call
+ <code>Class.forName("java.lang.String")</code>.
+ As long as the object whose class is being referenced is
+ pure Java, the code making the reference remains pure.</li>
+ </ol>
+ <li>Warning: possible hard-coded path: ...
+ <br/>When a String literal contains a common path separator
+ character (e.g. '/' or '\'), JavaPureCheck assumes that
+ it is a hard-coded path and that the class may not
+ contain portable code. While a human tester can verify
+ that the string is not a path, JavaPureCheck must be
+ conservative and issue a warning.</li>
+ </ol>
+ <p>Explanations:</p>
+ <ul>
+ <li>Class: org.xml.sax.helpers.ParserFactory</li>
+ <ul><li>Warning: method reference: java.lang.Class.forName(java.lang.String)</li></ul>
+ <ul><li>Explanation: The ParserFactory class is part of the standard SAX 1.0 distribution. The warning given that this class "may load impure class" is correct -- the ParserFactory class may load impure Java class files. However, the purpose of this utility class is to load parser classes by name and therefore cannot dynamically check the pureness of parser classes loaded in this fashion. Since the Xerces-J parser does not use this method directly, it is not a problem that concerns the Xerces-J parser. </li></ul>
+ <li>Class: org.apache.xml.serialize.SerializerFactory</li>
+ <ul><li>Warning: method reference: java.lang.Class.forName(java.lang.String)</li></ul>
+ <ul><li>Explanation: The SerializerFactory supports querying a system property to dynamically instantiate a serializer by class name. However, all of the serializer classes provided in this distribution are pure. The only way to load an impure serializer is if the user provided an impure serializer implementation.</li></ul>
+ <li>Class: org.apache.xml.serialize.OutputFormat</li>
+ <ul><li>Warning: possible hard-coded path: text/xml</li></ul>
+ <ul><li>Warning: possible hard-coded path: text/plain</li></ul>
+ <ul><li>Warning: possible hard-coded path: application/pdf</li></ul>
+ <ul><li>Warning: possible hard-coded path: text/html</li></ul>
+ <ul><li>Warning: possible hard-coded path: -//W3C//DTD XHTML 1.0 Strict//EN</li></ul>
+ <ul><li>Explanation: These strings are not filenames.</li></ul>
+ <li>Class: org.apache.xml.serialize.HTMLdtd</li>
+ <ul><li>Warning: method reference: java.lang.Class.forName(java.lang.String)</li></ul>
+ <ul><li>Explanation: Referencing class object that is pure Java.</li></ul>
+ <li>Class: org.apache.html.dom.HTMLDocumentImpl</li>
+ <ul><li>Warning: method reference: java.lang.Class.forName(java.lang.String)</li></ul>
+ <ul><li>Explanation: Referencing class object that is pure Java.</li></ul>
+ <li>Class: org.apache.xerces.readers.StringReader</li>
+ <ul><li>Warning: method reference: java.lang.Class.forName(java.lang.String)</li></ul>
+ <ul><li>Explanation: Referencing class object that is pure Java.</li></ul>
+ <li>Class: org.apache.xerces.parsers.DOMParser</li>
+ <ul><li>Warning: method reference: java.lang.Class.forName(java.lang.String)</li></ul>
+ <ul><li>Explanation: The DOMParser class allows the user to set the DOM implemenation to use, by name. However, the default DOM implementation is pure Java.</li></ul>
+ <ul><li>Explanation: Referencing class object that is pure Java.</li></ul>
+ <li>Class: org.apache.xerces.utils.CharDataChunk</li>
+ <ul><li>Warning: method reference: java.lang.Class.forName(java.lang.String)</li></ul>
+ <ul><li>Explanation: Referencing class object that is pure Java.</li></ul>
+ <li>Class: org.apache.xerces.utils.UTF8DataChunk</li>
+ <ul><li>Warning: method reference: java.lang.Class.forName(java.lang.String)</li></ul>
+ <ul><li>Explanation: Referencing class object that is pure Java.</li></ul>
+ </ul>
+ <p>The results file of the JavaPureCheck can be viewed by clicking <link idref="jpc">here</link>.</p>
+ <note>The samples were not checked with JavaPureCheck and are not
+ guaranteed to be pure Java. We reserve the right to write samples
+ in the future that are platform specific and therefore may not
+ pass as pure Java. The parser, however, will remain pure Java.</note>
</a>
</faq>
<faq title="Running on the Mac?">
<q>How do I get &javaparsername; to run on the Mac under MRJ?</q>
<a> <p><em>Prerequisites</em> (available from
<jump href="http://developer.apple.com/java/">http://developer.apple.com/java/</jump>):</p>
- <ul>
- <li>MRJ 2.1 (this is the most recent version of the JVM)</li>
- <li>MRJ SDK 2.1 (this is the most recent version of the Java developer tools)</li>
- </ul>
- <p><em>Instructions </em>(other variations would work also):</p>
- <ol>
- <li>Download the .tar.gz file containing &javaparsername;.</li>
- <li>Use Stuffit Expander(tm), Suntar, or some other Macintosh tool that
- <br/>supports the .tar.gz format to expand the downloaded file.</li>
- <li>JBindery, part of MRJ SDK 2.1, is used to create a double-clickable
- Java application with the necessary configuration information built in.
- It is analogous to writing a .bat or .sh script. </li>
- <li><em>To run the dom.DOMWriter example:</em></li>
- <ol>
- <li>Double click on JBindery to start it up.</li>
- <li>Click on the Classpath panel.</li>
- <li>Click on the "Add .zip File" button and add both the
- "Xerces-J.jar" and "Xerces-JSamples.jar" files.</li>
- <li>Click on the Command panel.</li>
- <li>Enter "dom.DOMWriter" as the Class name. Enter
- "data/personal.xml" in the Optional parameters box.</li>
- <li>Click on Save Settings button, pick a name such as "Run <code>dom.DOMWriter</code>"
- for the file, and <em>be sure</em> that "Save as Application"
- is selected (this is the default) and save the file.</li>
- <li>Quit JBindery.</li>
- <li>You can now double click on the file you created in step f to run the XJParse example.</li>
- </ol>
- </ol>
+ <ul>
+ <li>MRJ 2.1 (this is the most recent version of the JVM)</li>
+ <li>MRJ SDK 2.1 (this is the most recent version of the Java developer tools)</li>
+ </ul>
+ <p><em>Instructions </em>(other variations would work also):</p>
+ <ol>
+ <li>Download the .tar.gz file containing &javaparsername;.</li>
+ <li>Use Stuffit Expander(tm), Suntar, or some other Macintosh tool that
+ <br/>supports the .tar.gz format to expand the downloaded file.</li>
+ <li>JBindery, part of MRJ SDK 2.1, is used to create a double-clickable
+ Java application with the necessary configuration information built in.
+ It is analogous to writing a .bat or .sh script. </li>
+ <li><em>To run the dom.DOMWriter example:</em></li>
+ <ol>
+ <li>Double click on JBindery to start it up.</li>
+ <li>Click on the Classpath panel.</li>
+ <li>Click on the "Add .zip File" button and add both the
+ "Xerces-J.jar" and "Xerces-JSamples.jar" files.</li>
+ <li>Click on the Command panel.</li>
+ <li>Enter "dom.DOMWriter" as the Class name. Enter
+ "data/personal.xml" in the Optional parameters box.</li>
+ <li>Click on Save Settings button, pick a name such as "Run <code>dom.DOMWriter</code>"
+ for the file, and <em>be sure</em> that "Save as Application"
+ is selected (this is the default) and save the file.</li>
+ <li>Quit JBindery.</li>
+ <li>You can now double click on the file you created in step f to run the XJParse example.</li>
+ </ol>
+ </ol>
</a>
</faq>
<faq title="Visual Cafe exception error?">
1.5 +18 -34 xml-xerces/java/docs/faq-general.xml
Index: faq-general.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-general.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- faq-general.xml 2000/01/24 23:43:48 1.4
+++ faq-general.xml 2000/01/28 22:57:23 1.5
@@ -2,58 +2,41 @@
<!DOCTYPE faqs SYSTEM "sbk:/style/dtd/faqs.dtd">
<faqs title="General FAQs">
+
<faq title="New Features?">
<q>What are the new features?</q>
<a>
<p>Here are some of the new features in &javaparsername;:</p>
- <ul>
- <li>Support for SAX2 alpha</li>
- <li>Support for DOM Level 2 Core, Events, and Traversal</li>
- <li>Preliminary support for W3C XML Schema Language (validation
- only)</li>
- <li>Access to DTD information as a DOM Tree</li>
- <li>Improved Conformance</li>
- <li>Improved Performance</li>
- <li>Parser option control based on SAX2</li>
- <li>New "serialization" classes allow you output XML, HTML, and XHTML.</li>
- <li>New classes implement the HTML portion of the DOM Level 1 specification.</li>
- </ul>
+ <ul>
+ <li>Support for SAX2 alpha.</li>
+ <li>Support for DOM Level 2 Core, Events, Traversal, and Ranges.</li>
+ <li>Preliminary support for W3C XML Schema Language (validation only).</li>
+ <li>Access to DTD information as a DOM Tree.</li>
+ <li>Improved Conformance.</li>
+ <li>Improved Performance.</li>
+ <li>Parser option control based on SAX2.</li>
+ <li>New "serialization" classes allow you output XML, HTML, and XHTML.</li>
+ <li>New classes implement the HTML portion of the DOM Level 1 specification.</li>
+ </ul>
+ <anchor name="valid"/>
</a>
</faq>
+
<faq title="Validation">
-<!-- <anchor name="configure-validation"/> -->
<q>How do I turn on validation?</q>
<a>
<p>You can turn validation on and off via the SAX2
Configurable interface. This works for both the <code>SAXParser</code>
and <code>DOMParser</code> classes.<br/>
- The code snippet below shows how to turn validation on -- assume that <code>parser</code>
+ The code snippet below shows how to turn validation on -- assume that <ref>parser</ref>
is an instance of either
<code>org.apache.xerces.parsers.SAXParser</code> or
<code>org.apache.xerces.parsers.DOMParser</code>. <br/><br/>
- <code>((Configurable)parser).setFeature("http://xml.org/sax/features/validation", true);</code>
+ <code>((Configurable)parser).setFeature("http://xml.org/sax/features/validation", true);</code>
</p>
</a>
</faq>
- <faq title="Migrating from other XML parsers">
- <q>How do I migrate my code from other XML parsers?</q>
- <a>
- <p>To migrate your code from XML4J Version 2.0.x</p>
- Migrating from the version 2.0.x native SAX and DOM parser
- classes should be straight forward.
-<table>
-<tr><th>change this XML4J class</th><th>to this &javaparsername; class</th></tr>
-<tr><td>com.ibm.xml.parsers.SAXParser</td> <td>org.apache.xerces.parsers.SAXParser</td></tr>
-<tr><td>com.ibm.xml.parsers.ValidatingSAXParser</td> <td>org.apache.xerces.parsers.SAXParser + switch</td></tr>
-<tr><td>com.ibm.xml.parsers.NonValidatingDOMParser</td> <td>org.apache.xerces.parsers.DOMParser</td></tr>
-<tr><td>com.ibm.xml.parsers.DOMParser</td> <td>org.apache.xerces.parsers.DOMParser + switch</td></tr>
-</table>
-Table entries that say " + switch" mean that you should use the
-Configurable API to turn validation on. See the answer on turning on
-validation, <!-- <link idref="configure-validation"> -->above <!--
-</link> -->.
- </a>
- </faq>
+
<faq title="International Encodings">
<q>What international encodings are supported by &javaparsername;?</q>
<a>
@@ -108,4 +91,5 @@
</ul>
</a>
</faq>
+
</faqs>
1.2 +23 -5 xml-xerces/java/docs/faq-migrate.xml
Index: faq-migrate.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-migrate.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- faq-migrate.xml 2000/01/25 00:06:24 1.1
+++ faq-migrate.xml 2000/01/28 22:57:23 1.2
@@ -1,7 +1,7 @@
<?xml version="1.0" standalone="no"?>
<!DOCTYPE faqs SYSTEM "sbk:/style/dtd/faqs.dtd">
-<faqs title="Migrating to Xerces-Java">
+<faqs title="Migrating to &javaparsernamelong;">
<faq title="What should I be aware of when using various DOM parsers?">
<q>What should I be aware of when using various DOM parsers?</q>
<a><p>There are a couple of points to note when using the various
@@ -9,7 +9,7 @@
Xerces, Oracle and Sun XML parsers:</p>
<ol>
<li><em>Parsing methods:</em>
- <br/>The Xerces and Oracle parsers have a parser object that parses
+ <br/>The &javaparsername; and Oracle parsers have a parser object that parses
XML files and constructs a DOM tree which is queried
<ref>after</ref> parsing.
<br/>The Sun parser calls a static method on the
@@ -21,7 +21,7 @@
as well as parsing from <code>java.io.InputStream</code>
and <code>java.io.Reader</code> object.</li>
<li><em>Error handling:</em>
- <br/>The Xerces parser uses the SAX <code>ErrorHandler</code> mechanism
+ <br/>The &javaparsername; parser uses the SAX <code>ErrorHandler</code> mechanism
on all parser types, including DOM.
<br/>The Oracle parser only allows you to specify which
output stream or writer you want the error to be written.
@@ -30,14 +30,14 @@
An exceptions will be thrown if an error occurs during
parsing.</li>
<li><em>Validation:</em>
- <br/>The Xerces and Oracle DOM parsers use a method to
+ <br/>The &javaparsername; and Oracle DOM parsers use a method to
set validation.
<br/>Because of the way that DOM documents are constructed from XML files
in the Sun parser, validation is set via a parameter to the static
<code>createXmlDocument</code> method.</li>
<li><em>Standard versus proprietary features:</em>
<br/>If the user has written their programs using the W3C DOM API,
- then migrating to Xerces is easy. If however, the user takes
+ then migrating to &javaparsername; is easy. If however, the user takes
advantage of non-standard, proprietary features of the Oracle and Sun
parsers and DOM implementations, migration will be harder.
This document does not
@@ -206,4 +206,22 @@
</a>
</faq>
+
+ <faq title="Migrating from XML4J Version 2.0.x">
+ <q>How do I migrate my code from XML4J Version 2.0.x?</q>
+ <a>
+ <p>Migrating from the version 2.0.x native SAX and DOM parser
+ classes should be straight forward.</p>
+ <table>
+ <tr><th>change this XML4J class</th><th>to this &javaparsername; class</th></tr>
+ <tr><td>com.ibm.xml.parsers.SAXParser</td> <td>org.apache.xerces.parsers.SAXParser</td></tr>
+ <tr><td>com.ibm.xml.parsers.ValidatingSAXParser</td> <td>org.apache.xerces.parsers.SAXParser + switch</td></tr>
+ <tr><td>com.ibm.xml.parsers.NonValidatingDOMParser</td> <td>org.apache.xerces.parsers.DOMParser</td></tr>
+ <tr><td>com.ibm.xml.parsers.DOMParser</td> <td>org.apache.xerces.parsers.DOMParser + switch</td></tr>
+ </table>
+ <p>Table entries that say " + switch" mean that you should use the
+ Configurable API to turn validation on. See the answer in <link idref="faq-general" anchor="valid">Validation</link>.</p>
+ </a>
+ </faq>
+
</faqs>
1.7 +120 -100 xml-xerces/java/docs/faq-write.xml
Index: faq-write.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-write.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- faq-write.xml 2000/01/25 22:03:45 1.6
+++ faq-write.xml 2000/01/28 22:57:23 1.7
@@ -3,13 +3,8 @@
<faqs title="Writing Application FAQs">
<faq title="Creating a DOM Parser">
- <q>How do I create a parser that produces a DOM tree?</q>
- <a><p>To work with a parser that produces a DOM tree, you need to
- use the <code>DOMParser</code> class from
- <code>org.apache.xerces.parsers</code>. The code sample below
- shows you how to create a <code>DOMParser</code> instance and
- use it to parse an XML document.</p>
-
+ <q>How do I create a DOM parser?</q>
+ <a>
<source>import org.apache.xerces.parsers.DOMParser;
import org.w3c.dom.Document;
import org.xml.sax.SAXException;
@@ -28,52 +23,35 @@
se.printStackTrace();
} catch (IOException ioe) {
ioe.printStackTrace();
-}
-
-Document doc = parser.getDocument();
-
- ...</source>
-
- <p>Once you have the <code>Document</code> object, you can call any method on it as defined by the DOM specification.</p>
- </a>
+}</source>
+ </a>
</faq>
<faq title="Creating a SAX Parser">
- <q>How do I create a parser that uses the SAX API?</q>
- <a><p>To work with a parser that uses the SAX API, you need to
- use the <code>SAXParser</code> class from
- <code>org.apache.xerces.parsers</code>. You need to be sure
- that you provide classes that implement the SAX
- <code>DocumentHandler</code> and <code>ErrorHandler</code>
- interfaces. The code sample below shows how to create a
- <code>SAXParser</code> instance and use that instance to
- parse an XML document.</p>
-<source>import org.apache.xerces.parsers.SAXParser;
+ <q>How do I create a SAX parser?</q>
+ <a>
+<source>import org.xml.sax.Parser;
+import org.xml.sax.helpers.ParserFactory;
+import org.apache.xerces.parsers.DOMParser;
+import org.w3c.dom.Document;
import org.xml.sax.SAXException;
-import org.xml.sax.DocumentHandler;
-import java.io.IOException;
+import java.io.IOException;
...
-String xmlFile = "file:///Xerces-J/data/personal.xml";
+String parserClass = "org.apache.xerces.parsers.DOMParser";
-SAXParser parser = new SAXParser();
+String xmlFile = "file:///Xerces-J/data/personal.xml";
-DocumentHandler documentHandler = ... // you supply a class that implements the DocumentHandler interface
-ErrorHandler errorHandler = ... // you supply a class that implements the ErrorHandler interface
+Parser parser = ParserFactory.makeParser(parserClass);
try {
- parser.setDocumentHandler(documentHandler);
- parser.setErrorHandler(errorHandler)
parser.parse(xmlFile);
-
} catch (SAXException se) {
se.printStackTrace();
} catch (IOException ioe) {
- ioe.printStackTrace();
-}
-
- ...</source>
+ ioe.printStackTrace();
+}</source>
</a>
</faq>
@@ -89,29 +67,25 @@
</faq>
<faq title="Using lazy DOM">
<q>How do I use the lazy evaluating DOM implementation?</q>
- <a><p>The DOM parser class
- <code>org.apache.xerces.parsers.DOMParser</code> now uses a DOM
- implementation that can take advantage of lazy evaluation to
- improve performance. The setNodeExpansion call on these
- classes controls the use of lazy evaluation. There are two
- values for the argument to setNodeExpansion: FULL and
- DEFERRED(the default). </p>
- <p>If node expansion is set to FULL, then the DOM classes
- behave as they always have, creating all nodes in the DOM tree
- by the end of parsing.</p>
-
- <p>If node expansion is set to DEFERRED, nodes in the DOM tree
- are only created when they are accessed. This means that a
- call to getDocument will return a DOM tree that consists only
- of the Document node. When your program accesses a child of
- Document, the children of the Document node will be
- created. All the immediate children of a Node are created when
- any of that Node's children are accessed. This shortens the
- time it takes to parse an XML file and create a DOM tree. This
- also increases the time it takes to access a node that has not
- been created. After nodes have been created, they are cached,
- so this overhead only occurs on the first access to a
- Node. </p>
+ <a><p>The DOM parser class <code>org.apache.xerces.parsers.DOMParser</code> uses a
+ DOM implementation that can take advantage of lazy evaluation to
+ improve performance. There is also a mode where the parser creates
+ all of the nodes as the document is parsed. By default, the parser
+ uses the lazy evaluation DOM implementation.</p>
+ <p>Nodes in the DOM tree are only created when they are accessed.
+ The initial call to <code>getDocument()</code> will return a DOM tree that
+ consists only of the Document node. All of the immediate children
+ of a Node are created when any of that Node's children are accessed.
+ This shortens the time it takes to parse an XML file and create a DOM
+ tree at the expense of requiring more memory during parsing and
+ traversing the document.</p>
+ <p>The lazy evaluation feature is set using the SAX2 Configurable
+ interface. To turn off this feature, use the following code:</p>
+<source>DOMParser parser = new DOMParser();
+parser.setFeature("http://apache.org/xml/features/dom/defer-node-expansion", false);</source>
+ <p>To turn the lazy evaluation feature back on, use the following code:</p>
+
+<source>parser.setFeature("http://apache.org/xml/features/dom/defer-node-expansion", true);</source>
</a>
</faq>
@@ -147,7 +121,7 @@
</a>
</faq>
- <faq title="Why does "non-validating" not mean "well-formedness checking only"?">
+ <faq title="What does "non-validating" mean?">
<q>Why does "non-validating" not mean "well-formedness checking only"?</q>
<a><p>Using a "non-validating" parser does not mean that only well-formedness
checking is done! There are still many things that the XML specification
@@ -194,16 +168,65 @@
before accessing it over the network.</li>
<li>Do not reference an external DTD or internal DTD subset at all.
In this case, no DTD will be read.</li>
+ <li>Use a custom <code>EntityResolver</code> and keep common
+ DTDs in a memory buffer.</li>
</ul>
</a>
</faq>
- <faq title="How do access the DOM Level 2 functionality">
- <q>How do I access the DOM Level 2 functionality</q>
- <a><p>Because the DOM Level 2 spec is not frozen yet, the interfaces
- for DOM Level 2 can be found in the package org.apache.xerces.domx
- and its subpackages.</p></a>
- </faq>
+ <faq title="How do I access the DOM Level 2 functionality?">
+ <q>How do I access the DOM Level 2 functionality?</q>
+ <a><p>The <jump href="http://www.w3.org/TR/DOM-Level-2/">DOM Level 2</jump>
+ specification is at the stage of
+ "Candidate Recommendation" (CR), which allows feedback from implementors
+ before it becomes a "Recommedation". It is comprised of "core"
+ functionality, which is mainly the DOM
+ <jump href="http://www.w3.org/TR/REC-xml-names/">Namespaces</jump> implementation,
+ and a number of optional modules (called Chapters in the spec).</p>
+ <p>Please refer to:</p>
+ <p><jump href="http://www.w3.org/TR/DOM-Level-2/">
+ http://www.w3.org/TR/DOM-Level-2/</jump> for the
+ latest DOM Level 2 specification.</p>
+ <p>The following DOM Level 2 modules are fully implemented in &javaparsername;: </p>
+ <ul>
+ <li><jump href="http://www.w3.org/TR/DOM-Level-2/core.html">
+ Chapter 1: Core</jump> - most of these enhancements are for
+ Namespaces, and can be acessed through additional functions which
+ have been added directly to the <ref>org.w3c.dom.*</ref> classes.</li>
+
+ <li><jump href="http://www.w3.org/TR/DOM-Level-2/events.html">
+ Chapter 6: Events</jump> - The <ref>org.w3c.dom.events.EventTarget</ref>
+ interface is implemented by all <code>Nodes</code> of the DOM.
+ The &javaparsername; DOM implementation handles all of the event
+ triggering, capture and flow.</li>
+
+ <li><jump href="http://www.w3.org/TR/DOM-Level-2/traversal.html">
+ Chapter 7: Traversal</jump> - The Traversal module interfaces
+ are located in <ref>org.w3c.dom.traversal</ref>.
+ The <code>NodeIterator</code> and <code>TreeWalker</code>, and
+ <code>NodeFilter</code> interfaces have been supplied to allow
+ traversal of the DOM at a higher-level. Our DOM Document
+ implementation class, <code>DocumentImpl</code> class now
+ implements <code>DocumentTraversal</code>, which supplies the
+ factory methods to create the iterators and treewalkers.</li>
+
+ <li><jump href="http://www.w3.org/TR/DOM-Level-2/range.html">
+ Chapter 8. Range</jump> - The Range module interfaces are
+ located in <ref>org.w3c.dom.range</ref>. The Range interface
+ allows you to specify ranges or selections using boundary
+ points in the DOM, along with functions (like delete,
+ clone, extract..) that can be performed on these ranges.
+ Our DOM Document implementation class, <code>DocumentImpl</code>
+ class now implements <code>DocumentRange</code>, that supplies
+ the factory method to create a <code>Range</code>.</li>
+ </ul>
+ <note>Since the DOM Level 2 is still in the CR phase, some changes
+ to these specs are still possible. The purpose of this phase is to
+ provide feedback to the W3C, so that the specs can be clarified and
+ implementation concerns can be addressed.</note>
+ </a>
+ </faq>
+
<faq title="How do I read data from a stream as it arrives?">
<q>How do I read data from a stream as it arrives?</q>
<a><p>For performance reasons, all the standard Xerces processing
@@ -215,38 +238,36 @@
and override <code>createCharReader</code> and
<code>createUTF8Reader</code> as shown below.
</p>
- <source>
-public class StreamingCharFactory extends org.apache.xerces.readers.DefaultReaderFactory {
- public XMLEntityHandler.EntityReader createCharReader(XMLEntityHandler entityHandler,
- XMLErrorReporter errorReporter,
- boolean sendCharDataAsCharArray,
- Reader reader,
- StringPool stringPool) throws Exception
- {
- return new org.apache.xerces.readers.StreamingCharReader(entityHandler, errorReporter, sendCharDataAsCharArray, reader, stringPool);
- }
-
- public XMLEntityHandler.EntityReader createUTF8Reader(XMLEntityHandler entityHandler,
- XMLErrorReporter errorReporter,
- boolean sendCharDataAsCharArray,
- InputStream data,
- StringPool stringPool) throws Exception
- {
- XMLEntityHandler.EntityReader reader;
- reader = new org.apache.xerces.readers.StreamingCharReader(entityHandler, errorReporter, sendCharDataAsCharArray, new InputStreamReader(data, "UTF8"), stringPool);
- return reader;
- }
-
-}
- </source>
- <p>
- In your program, after you instantiate a parser class, replace
+<source>public class StreamingCharFactory extends org.apache.xerces.readers.DefaultReaderFactory {
+ public XMLEntityHandler.EntityReader createCharReader(XMLEntityHandler entityHandler,
+ XMLErrorReporter errorReporter,
+ boolean sendCharDataAsCharArray,
+ Reader reader,
+ StringPool stringPool) throws Exception
+ {
+ return new org.apache.xerces.readers.StreamingCharReader(entityHandler,
+ errorReporter, sendCharDataAsCharArray, reader, stringPool);
+ }
+
+ public XMLEntityHandler.EntityReader createUTF8Reader(XMLEntityHandler entityHandler,
+ XMLErrorReporter errorReporter,
+ boolean sendCharDataAsCharArray,
+ InputStream data,
+ StringPool stringPool) throws Exception
+ {
+ XMLEntityHandler.EntityReader reader;
+ reader = new org.apache.xerces.readers.StreamingCharReader(entityHandler,
+ errorReporter, sendCharDataAsCharArray,
+ new InputStreamReader(data, "UTF8"), stringPool);
+ return reader;
+ }
+
+}</source>
+ <p>In your program, after you instantiate a parser class, replace
the <code>DefaultReaderFactory</code> with <code>StreamingCharFactory</code>, and be
sure to wrap the <code>InputStream</code> that you are reading
- from with an <code>InputStreamReader</code>.
- </p>
- <source>
-InputStream in = ... ;
+ from with an <code>InputStreamReader</code>.</p>
+<source>InputStream in = ... ;
SAXParser p = new SAXParser();
DocumentHandler h = ... ;
// set the correct reader factory
@@ -254,8 +275,7 @@
p.setDocumentHandler(h);
// be sure to wrap the input stream in an InputStreamReader.
-p.parse(new InputSource(new InputStreamReader(in)));
- </source>
+p.parse(new InputSource(new InputStreamReader(in)));</source>
</a>
</faq>
</faqs>
1.3 +1 -1 xml-xerces/java/docs/feedback.xml
Index: feedback.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/feedback.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- feedback.xml 1999/12/20 17:41:03 1.2
+++ feedback.xml 2000/01/28 22:57:23 1.3
@@ -7,7 +7,7 @@
<p>If you are submitting a bug (and bug reports are definitely appreciated!),
please provide the following information:</p>
<ul>
- <li>Version number of &javaparsername; (1.0.0?) </li>
+ <li>Version number of &javaparsername; (&javaparserversion;?) </li>
<li>Version number of JDK (1.1.8? 1.2?)</li>
<li>Sample XML file that causes the bug</li>
<li>Sample Schema file (if required to recreate the bug)</li>
1.4 +8 -3 xml-xerces/java/docs/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/install.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- install.xml 1999/12/29 01:07:44 1.3
+++ install.xml 2000/01/28 22:57:23 1.4
@@ -7,14 +7,15 @@
platforms and operating systems. You need to run the Java
<ref>jar</ref> command to unpack the distribution.</p>
<ul>
- <li>jar &javaparserdistname;.jar</li>
+ <li>jar xf &javaparsername;-bin.&javaparserversion;.jar</li>
+ <li>jar xf &javaparsername;-src.&javaparserversion;.jar</li>
<li>This command creates a "&javaparserdirectory;" sub-directory in the current directory containing all the files.</li>
</ul>
</s2>
<s2 title="Files in this release">
<table>
- <tr><td>bin/Xerces.jar</td><td>Jar file containing all the parser class files</td></tr>
- <tr><td>bin/XercesSamples.jar</td><td>Jar file containing all sample class files</td></tr>
+ <tr><td>bin/xerces.jar</td><td>Jar file containing all the parser class files</td></tr>
+ <tr><td>bin/xercesSamples.jar</td><td>Jar file containing all sample class files</td></tr>
<tr><td>Readme.html</td><td>This file</td></tr>
<tr><td>license.html</td><td>license for &javaparsername;</td></tr>
<tr><td>w3c_copyright_software.html</td><td>W3C Copyright Notice for DOM</td></tr>
@@ -24,5 +25,9 @@
<tr><td>src/</td><td>Source files</td></tr>
<tr><td>samples/</td><td>Directory containing sample programs</td></tr>
</table>
+ <note>To use &javaparsername; you do not need the source files.
+ However the source jar file contains the full documentation and you will
+ want to have that available. so even if you do not plan on looking at the
+ source files you still need to download the source jar file.</note>
</s2>
</s1>
1.5 +31 -23 xml-xerces/java/docs/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/readme.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- readme.xml 2000/01/25 22:03:45 1.4
+++ readme.xml 2000/01/28 22:57:23 1.5
@@ -1,40 +1,50 @@
<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
-<s1 title="&javaparsername;">
- <s2 title="&javaparsername; &javaparserversion; Release">
- <p>The &javaparsername; &javaparserversion; release contains advanced
- parser functionality, such as XML Schema, DOM Level 2, and SAX version 2,
- in addition to supporting the industry-standard DOM Level 1 and SAX version 1
+<s1 title="&javaparsernamelong; Readme">
+ <s2 title="&javaparsernamelong; &javaparserversion; Release">
+ <p>The &javaparsernamelong; &javaparserversion; supports
+ <jump href="http://www.w3.org/TR/1998/REC-xml-19980210">XML 1.0</jump>
+ recommendation and the contains advanced parser functionality, such as
+ <jump href="http://www.w3.org/XML/Group/Schemas.html">XML Schema</jump>,
+ <jump href="http://www.w3.org/TR/DOM-Level-2/">DOM Level 2 version 1.0</jump>, and
+ <jump href="http://www.megginson.com/SAX/SAX2/">SAX Version 2</jump>,
+ in addition to supporting the industry-standard
+ <jump href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/level-one-core.html">DOM Level 1</jump> and
+ <jump href="http://www.megginson.com/SAX/index.html">SAX version 1</jump>
APIs.</p>
<p>
<!--
&javaparsername; &javaparserversion; is the first in a series of ongoing updates -
Watch <jump href="http://xml.apache.org">xml.apache.org</jump>
for new updates. -->
- Note that because some of the standards, notably
- XML Schema, are still not complete, the stable API will definitely be
- different from its current form in &javaparsername; &javaparserversion;. This is your chance to give us
+
+ Note that because some of the standards,
+ are still not complete, the stable API will definitely be
+ different from its current form in &javaparsername; &javaparserversion;.
+ This is your chance to give us
feedback on the features that are important to you, and let us know
whether the APIs that we are providing are the right ones. Please
direct your feedback to the &javaparsername; mailing list.</p>
+ <p>The &javaparserversion; release benefits from the
+ <jump href="http:://xml.apache.org">xml.apache.org</jump> collaboration.
+ It includes Assaf Arkin's serialization and HTML DOM contributions.
+ See the <link idref="releases">release</link> information</p>
</s2>
<s2 title="License Information">
<p>The &javaparsername; &javaparserversion; release is available in both source code
- and precompiled binary (JAR files) form. &javaparsername;
- &javaparserversion; is licensed under the terms of Version
- 1.1 of the <jump href="http://xml.apache.org/dist/License.txt">Apache Software License</jump></p>
+ and precompiled binary (JAR files) form.</p>
</s2>
<s2 title="Applications of the &javaparsername; Parser">
<p>The rich generating and validating capabilities allow the &javaparsername;
Parser to be used for: </p>
<ul>
- <li>Building XML-savvy Web servers </li>
+ <li>Building XML-savvy Web servers. </li>
<li>The next generation of vertical applications which will use
XML as their data format. </li>
- <li>On-the-fly validation for creating XML editors </li>
- <li>Ensuring the integrity of e-business data expressed in XML </li>
+ <li>On-the-fly validation for creating XML editors. </li>
+ <li>Ensuring the integrity of e-business data expressed in XML. </li>
<li>Building truly internationalized XML applications. </li>
</ul>
</s2>
@@ -48,15 +58,12 @@
<s2 title="DOM Level 2 (alpha) Support">
<p>This release include support for the
<jump href="http://www.w3.org/TR/WD-DOM-Level-2">DOM Level 2 Core</jump> and
- <jump href="http://www.w3.org/TR/WD-DOM-Level-2">DOM Level 2 Traversal</jump> APIs.
- We will be expanding our DOM Level 2 support to include all of DOM Level 2. At the moment, the DOM
- Level 2 Traversal API's live in the org.apache.xerces.dom.domx.traversal
- package.</p>
+ <jump href="http://www.w3.org/TR/WD-DOM-Level-2">DOM Level 2 Traversal</jump> APIs.</p>
</s2>
<s2 title="SAX 2 (alpha) Support">
<p>This release includes support for the <jump href="http://www.megginson.com/SAX/SAX2/">
- SAX Version 2</jump> API's which are being discussed on the
- <jump href="http://www.lists.ic.ac.uk/hypermail/xml-dev/">XML-DEV</jump> mailing list.
+ SAX Version 2</jump> API's which are being discussed on the
+ <jump href="http://www.lists.ic.ac.uk/hypermail/xml-dev/">xml-dev</jump> mailing list.
These API's are still
under development, so they are subject to change in the future.</p>
</s2>
@@ -64,8 +71,9 @@
<p>&javaparsername; &javaparserversion; uses a collection of methods to configure
various settings in the parser. This release includes a new mechanism
for setting parser switches. This mechanism uses the SAX2 Configurable
- interface. We have defined a series of properties and features for the
- options available in &javaparsername;. The list of features can be found
- <link idref="features">here</link>.</p>
+ interface. We have defined a series of
+ <link idref="properties">properties</link> and
+ <link idref="features">features</link> for the &javaparsername;
+ options. </p>
</s2>
</s1>
1.3 +4 -4 xml-xerces/java/docs/sam-iterator.xml
Index: sam-iterator.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/sam-iterator.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- sam-iterator.xml 2000/01/24 23:43:48 1.2
+++ sam-iterator.xml 2000/01/28 22:57:23 1.3
@@ -3,12 +3,12 @@
<s1 title="IteratorView Sample">
<s2 title="IteratorView">
- <p>The <code>IteratorView></code> is an interactive UI sample that displays the DOM tree. It
+ <p>The <code>IteratorView</code> is an interactive UI sample that displays the DOM tree. It
shows the progress of the iteration by moving the selection within the DOM tree.
Buttons act as a control panel, allowing the user to interactively iterate through
the tree, remove nodes, add nodes, and view the results immediately in the tree.</p>
- <p>The <code>IteratorView></code> uses an example filter, <code>NameNodeFilter</code>, that can be controlled
- from the UI and a DOMTreeFull class that displays the full DOM tree with all
+ <p>The <code>IteratorView</code> uses an example filter, <code>NameNodeFilter</code>, that can be controlled
+ from the UI and a <code>DOMTreeFull</code> class that displays the full DOM tree with all
the nodes.</p>
<p>The controls are called through to to the corresponding iterator function. If you
@@ -18,7 +18,7 @@
<s3 title="Iterator Group">
<ul>
<li>Next - calls the <code>next()</code> functions and selects the next node in the tree.</li>
- <li>Previous - calls the <code>previous()</code> function a and selects the previous node in
+ <li>Previous - calls the <code>previous()</code> function and selects the previous node in
the tree.</li>
</ul>
</s3>
1.5 +69 -11 xml-xerces/java/docs/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/samples.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- samples.xml 2000/01/24 23:43:48 1.4
+++ samples.xml 2000/01/28 22:57:23 1.5
@@ -6,14 +6,18 @@
<p>There are two new samples to test and demonstrate the new DOM2
Traversal implementation: </p>
<ul>
+ <li><link idref="domcount">DOMCount</link></li>
+ <li><link idref="domcount">SAXCount</link></li>
+ <li><link idref="domwriter">DOMWriter</link></li>
+ <li><link idref="domwriter">SAXWriter</link></li>
+ <li><link idref="domfilter">DOMFilter</link></li>
<li><link idref="iterator">IteratorView</link></li>
<li><link idref="tree">TreeWalker</link></li>
+ <li><link idref="treeview">TreeViewer</link></li>
</ul>
</s2>
<s2 title="Caveats">
- <note>Make sure that &javaparsername; and a JDK are loaded on
- your computer before running any of the sample applications.</note>
- <note>&javaparsername;: Running the sample applications
+ <note>&javaparsername;: Running the sample applications
requires that you have already loaded the &javaparsername; software on
your computer.</note>
<note>Java: Running the sample applications require that your computer has a
@@ -32,26 +36,80 @@
and replace Windows directory separator '\' (backslash)
with '/' (forward slash).</note>
</s2>
+
+ <s2 title="DOMCount Sample">
+ <p><link idref="domcount">DOMCount</link> parses your input file,
+ and outputs the total parse time,
+ along with counts of elements, attributes, text characters, and ignorable
+ whitespace characters. DOMCount displays errors and
+ warnings that occur during parsing.</p>
+ <p>DOMCount uses either the validating or non-validating DOM parser.</p>
+ </s2>
+
+ <s2 title="SAXCount Sample">
+ <p><link idref="domcount">SAXCount</link> parses your input file,
+ and outputs the total parse time,
+ along with counts of elements, attributes, text characters, and
+ ignorable whitespace characters. SAXCount displays errors and
+ warnings that occur during parsing.</p>
+ <p>SAXCount uses either the validating or non-validating SAX parser.</p>
+ </s2>
+
+ <s2 title="DOMWriter Sample">
+ <p><link idref="domwriter">DOMWriter</link> parses a file, and
+ prints it out in XML format.
+ The command line option, -c, is used to print files in
+ "canonical" XML format, so that two XML documents can be compared.
+ They also display any errors or warnings that occurred during the
+ parse. DOMWriter uses either the validating or non-validating DOM parser.
+ DOMWriter also provides a feature to set the output Java encoding
+ through the -e switch.</p>
+ </s2>
+
+ <s2 title="SAXWriter Sample">
+ <p><link idref="domwriter">SAXWriter</link> parses a file, and
+ prints it out in XML format. The command
+ line option, -c, is used to print files in "canonical" XML format,
+ so that two XML documents can be compared. They also display any
+ errors or warnings that occurred during the parse. SAXWriter uses
+ either the validating or non-validating SAX parser.</p>
+ </s2>
+
+ <s2 title="DOMFilter Sample">
+ <p><link idref="domfilter">DOMFilter</link> shows you how to
+ search for specific elements in
+ your XML document. It uses <code>getElementsByTagName()</code>
+ to traverse the DOM tree, looking for elements or attributes that
+ match your specification.</p>
+ </s2>
+
<s2 title="IteratorView Sample">
- <p>The <code>IteratorView</code> is an interactive UI sample that displays the DOM tree. It
+ <p><link idref="iterator">IteratorView</link> is an interactive
+ UI sample that displays the DOM tree. It
shows the progress of the iteration by moving the selection within the DOM tree.
Buttons act as a control panel, allowing the user to interactively iterate through
the tree, remove nodes, add nodes, and view the results immediately in the tree.</p>
- <p>The <code>IteratorView</code> uses an example filter, <code>NameNodeFilter</code>, that can be controlled
+ <p>The <code>IteratorView</code> uses an example filter,
+ <code>NameNodeFilter</code>, that can be controlled
from the UI and a <code>DOMTreeFull</code> class that displays the full DOM tree with all
the nodes.</p>
- <p><link idref="iterator">IteratorView page</link></p>
</s2>
+
<s2 title="TreeWalker Sample">
- <p>The <code>TreeWalkerviewView</code> is an interactive UI sample that displays the DOM
+ <p><link idref="tree">TreeWalkerviewView</link> is an interactive UI sample that displays the DOM
tree. It show the progress of the tree traversal by moving the selection within the
DOM tree. Buttons act as a control panel, allowing the user to interactively
traverse the tree, remove nodes, add nodes, and view the results immediately in
the tree.</p>
- <p>The <code>TreeWalkerviewView</code> uses an example filter, <code>NameNodeFilter</code>, that can be
- controlled from the UI and a <code>DOMTreeFull</code> class that displays the full DOM tree
- with all the nodes.</p>
- <p><link idref="tree">TreeWalkerView page</link></p>
+ <p>The <code>TreeWalkerviewView</code> uses an example filter,
+ <code>NameNodeFilter</code>, that can be
+ controlled from the UI and a <code>DOMTreeFull</code> class that
+ displays the full DOM tree with all the nodes.</p>
+ </s2>
+
+ <s2 title="Treeviewer Sample">
+ <p><link idref="tree">TreeViewer</link> displays the input XML file in a graphical tree-style
+ interface. It will also highlight lines have well-formedness or validation errors.</p>
</s2>
</s1>
1.4 +12 -10 xml-xerces/java/docs/schema.xml
Index: schema.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/schema.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- schema.xml 2000/01/24 23:43:48 1.3
+++ schema.xml 2000/01/28 22:57:23 1.4
@@ -5,22 +5,24 @@
<s2 title="Disclaimer">
<p>This package contains an implementation of the W3C XML
Schema language. This implementation is experimental. The
- XML Schema language is still in working draft stage: you
+ <jump href="http://www.w3.org/XML/Group/Schemas.html">XML Schema</jump>
+ language is still in working draft stage: you
should not consider this implementation complete or correct.
- The limitations of this implementation are detailed below --
- please read this document before using this package.</p>
+ The limitations of this implementation are detailed below.
+ Please read this document before using this package.</p>
</s2>
<s2 title="Introduction">
- <p>This package contains an implementation of a subset
- of the W3C XML Schema Language as specified in the 24
- September 1999 Working Draft. The parsers contained in this
+ <p>This package contains an implementation of a subset of the
+ <jump href="http://www.w3.org/XML/Group/Schemas.html">
+ W3C XML Schema Language</jump> as specified in the 17
+ December 1999 Working Draft. The parsers contained in this
package are able to read and validate XML documents with the
grammar specified in either DTD or XML Schema format. There
is no functionality for accessing typed data.</p>
<p>We are making this package available in order to get
feedback on the features in the XML Schema language
- design and on representing an XML document's grammar
- as part of the document's DOM tree. We intend to update
+ design and on representing an XML document's grammar
+ as part of the document's DOM tree. We intend to update
this package until it implements all of the functionality
of the then current XML Schema Working Draft. If you are
interested in a particular unimplemented feature, we welcome
@@ -28,7 +30,7 @@
</s2>
<s2 title="Limitations">
<p>The XML Schema implementation in this package is a
- subset of the features defined in the 24 September 1999
+ subset of the features defined in the 17 December 1999
XML Schema Working Drafts.</p>
</s2>
<s2 title="Structure Limitations">
@@ -79,7 +81,7 @@
<p>Documents that use XML Schema grammars specify the location of the
grammar using an xmlns attribute attached to the root / top-level element
in the document. Here is an example: </p>
-<source><document xmlns=&document.xsd>
+<source><document xmlns="document.xsd">
...
</document></source>
<p>Another requirement is that the XML Schema document's grammar must