You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by tw...@locus.apache.org on 2000/01/25 00:43:49 UTC
cvs commit: xml-xerces/java/docs faq-build.xml faq-common.xml faq-general.xml faq-write.xml features.xml properties.xml sam-iterator.xml sam-tree.xml samples.xml schema.xml y2k.xml
twl 00/01/24 15:43:49
Modified: java/docs faq-build.xml faq-common.xml faq-general.xml
faq-write.xml features.xml properties.xml
sam-iterator.xml sam-tree.xml samples.xml
schema.xml y2k.xml
Log:
Update docs for 1.0.2
Revision Changes Path
1.3 +9 -9 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.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- faq-build.xml 1999/12/20 17:41:02 1.2
+++ faq-build.xml 2000/01/24 23:43:48 1.3
@@ -2,14 +2,14 @@
<!DOCTYPE faqs SYSTEM "sbk:/style/dtd/faqs.dtd">
<faqs title="Building and Running FAQs">
- <faq title="Swing?">
+ <faq title="Swing version?">
<q>Which version of Swing is required?</q>
<a> <p>This release uses Swing 1.1 (JFC 1.1).
Swing is only used by the sample programs and is not
required by the parser itself.</p>
</a>
</faq>
- <faq title="Recompling?">
+ <faq title="Recompling source files?">
<q>How do I recompile the source files?</q>
<a> <p>To build &javaparsername; on Windows, you need a copy of Cygnus's Cygwin.
See <jump href="http://sourceware.cygnus.com/cygwin">http://sourceware.cygnus.com/cygwin</jump>.
@@ -28,7 +28,7 @@
</p>
</a>
</faq>
- <faq title="Regenerating?">
+ <faq title="Regenerating API documention?">
<q>How do I regenerate the api documentation?</q>
<a> <p>To regenerate the api documentation, you need to set up
your environment to build &javaparsername;. Instead of typing 'make', you
@@ -44,7 +44,7 @@
</a>
</faq>
-->
- <faq title="Visual Age?">
+ <faq title="How do I use Visual Age?">
<q>How do I import &javaparsername; into Visual Age for Java</q>
<a>
<ul>
@@ -81,9 +81,9 @@
</ul>
</a>
</faq>
- <faq title="100% Pure Java?">
+ <faq title="100% Pure Java compliant?">
<q>Is this &javaparsername; version 100% pure Java compliant?</q>
- <a> <p>blah
+ <a> <p>tba
</p>
</a>
</faq>
@@ -112,7 +112,7 @@
<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 dom.DOMWriter"
+ <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>
@@ -121,9 +121,9 @@
</ol>
</a>
</faq>
- <faq title="Visual Cafe Error?">
+ <faq title="Visual Cafe exception error?">
<q>Why do I get ArrayIndexOutOfBoundsException in the Symantec Visual Cafe debugger?</q>
- <a> <p>Visual Cafe's debugger is set to trap <code>ArrayIndexOutOfBoundsException</code>'s by
+ <a> <p>The Visual Cafe debugger is set to trap <code>ArrayIndexOutOfBoundsException</code> exceptions by
default. &javaparsername; uses <code>ArrayIndexOutOfBoundsException</code> internally to signal
exceptional, but not erroneous conditions. In order to run &javaparsername;2 inside
Visual Cafe's debugger, you need to turn off the trapping of these
1.3 +13 -9 xml-xerces/java/docs/faq-common.xml
Index: faq-common.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-common.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- faq-common.xml 1999/12/20 17:41:02 1.2
+++ faq-common.xml 2000/01/24 23:43:48 1.3
@@ -2,10 +2,10 @@
<!DOCTYPE faqs SYSTEM "sbk:/style/dtd/faqs.dtd">
<faqs title="Common Problems">
- <faq title="Parsing Generated an Error">
- <q>I tried to use &javaparsername; to parse HTML, and it generated an error. What did I do wrong?</q>
+ <faq title="Parsing HTML Generated an Error.">
+ <q>I tried to use &javaparsername; to parse an HTML file and it generated an error. What did I do wrong?</q>
<a><p>Unfortunately, HTML does not, in general, follow the XML grammar rules.
- Most HTML is actually not well-formed XML. Therefore, the XML parser
+ Most HTML files do not meet the XML style quidelines. Therefore, the XML parser
generates XML well-formedness errors.</p>
<p>Typical errors include:</p>
<ul>
@@ -13,10 +13,14 @@
<li>Missing closing slash on <IMG HREF="foo" <em>/</em>> (not required in HTML)</li>
<li>Missing quotes on attribute values, e.g. <IMG width="600"> (not generally required in HTML)</li>
</ul>
+ <p>HTML must match the XHTML standard for well-formedness before it
+ can be parsed by Xerces-J or any other XML parser. You can find the
+ <jump href="http://www.w3c.org/TR/1999/PR-xhtml1-19991210">XHTML standard</jump>
+ on the <jump href="http://www.w3c.org">W3C web site</jump>.</p>
</a>
</faq>
<faq title="UTF-8 Character Error">
- <q>I get an error: "invalid UTF-8 character"</q>
+ <q>I get an "invalid UTF-8 character" error.</q>
<a><p>There are many Unicode characters that are not allowed in an XML document,
according to the XML spec. Typical disallowed characters are control
characters, even if you escape them using the Character Reference form:
@@ -24,13 +28,13 @@
<jump href="http://www.w3.org/TR/REC-xml#charsets">2.2</jump> and
<jump href="http://www.w3.org/TR/REC-xml#sec-references">4.1</jump>
for details. If the parser is generating this error, it is very likely
- that there's a character in there that you can not see.
+ that there is a character in the file that you can not see.
You can generally use a UNIX command like "od -hc" to find it.</p>
</a>
</faq>
<faq title="Error Accessing EBCDIC XML Files">
- <q>I get an error when I access EBCDIC XML files -- what's happening?</q>
+ <q>I get an error when I access EBCDIC XML files, what is happening?</q>
<a><p>If an XML document/file is not UTF-8, then you MUST specify the encoding.
When transcoding a UTF8 document to EBCDIC, remember to change this:</p>
<ul>
@@ -42,9 +46,9 @@
</a>
</faq>
<faq title="EOF Character Error">
- <q>I get an error on the EOF character (0x1A) -- what's happening?</q>
- <a><p>No, the parser isn't broken. You're probably using the <em>LPEX</em>
- editor, which automatically inserts an End-of-file character at the end of your
+ <q>I get an error on the EOF character (0x1A) -- what is happening?</q>
+ <a><p>You are probably using the <em>LPEX</em>
+ editor, which automatically inserts an End-of-file character (0x1A) at the end of your
XML document (other editors might do this as well). Unfortunately, the
EOF character (0x1A) is an illegal character according to the XML specification,
and &javaparsername; correctly generates an error.</p>
1.4 +2 -2 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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq-general.xml 1999/12/29 01:07:43 1.3
+++ faq-general.xml 2000/01/24 23:43:48 1.4
@@ -63,8 +63,8 @@
<li>IBM-1208</li>
<li>ISO Latin-1 (ISO-8859-1)</li>
<li>ISO Latin-2 (ISO-8859-2) [Bosnian, Croatian, Czech,
- <br/>Hungarian, Polish, Romanian, Serbian (in Latin transcription),
- <br/>Serbocroatian, Slovak, Slovenian, Upper and Lower Sorbian]</li>
+ Hungarian, Polish, Romanian, Serbian (in Latin transcription),
+ Serbocroatian, Slovak, Slovenian, Upper and Lower Sorbian]</li>
<li>ISO Latin-3 (ISO-8859-3) [Maltese, Esperanto]</li>
<li>ISO Latin-4 (ISO-8859-4)</li>
<li>ISO Latin Cyrillic (ISO-8859-5)</li>
1.5 +23 -54 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.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- faq-write.xml 1999/12/30 03:57:36 1.4
+++ faq-write.xml 2000/01/24 23:43:48 1.5
@@ -11,8 +11,7 @@
this string to the <code>org.xml.sax.helpers.ParserFactory.makeParser()</code>
method to instantiate it. This method is useful if your application will need to switch between different parser configurations. The code snippet shown below is using this method to instantiate a DOMParser.</p>
- <source>
-import org.xml.sax.Parser;
+<source>import org.xml.sax.Parser;
import org.xml.sax.helpers.ParserFactory;
import org.apache.xerces.parsers.DOMParser;
import org.w3c.dom.Document;
@@ -38,8 +37,7 @@
Document doc = ((DOMParser) parser).getDocument();
- ...
- </source>
+ ...</source>
<p>The second way to instantiate a parser class is to <em>explicitly
instantiate</em> the parser class, as shown in this example,
@@ -47,8 +45,7 @@
exactly which parser configuration you need, and you are sure
that you will not need to switch configurations.</p>
- <source>
-import org.apache.xerces.parsers.DOMParser;
+<source>import org.apache.xerces.parsers.DOMParser;
import org.w3c.dom.Document;
import org.xml.sax.SAXException;
import java.io.IOException;
@@ -70,12 +67,12 @@
// The next line is only for DOM Parsers
Document doc = parser.getDocument();
- ...
- </source>
+ ...</source>
<p>Once you have the Document object, you can call any method on it as defined by the DOM specification.</p>
</a>
</faq>
+
<faq title="Creating a DOM Parser">
<q>How do I create a DOM parser?</q>
<a><p>Use one of the methods in the question above, and use
@@ -84,6 +81,7 @@
<code>getDocument()</code> method on the parser instance.</p>
</a>
</faq>
+
<faq title="Creating a SAX Parser">
<q>How do I create a SAX parser?</q>
<a><p>Use one of the methods in the question above, and use
@@ -92,6 +90,7 @@
methods to set the various handlers provided by SAX. </p>
</a>
</faq>
+
<faq title="Controlling parser options">
<q>How do I control the various parser options?</q>
<a><p>For this release, all of the parser control API's have
@@ -129,6 +128,7 @@
Node. </p>
</a>
</faq>
+
<faq title="Handling Errors">
<q>How do handle errors?</q>
<a><p>When you create a parser instance, the default error handler does nothing.
@@ -139,6 +139,7 @@
DOM based or SAX based parser.</p>
</a>
</faq>
+
<faq title="Controlling Entity Representation">
<q>How can I control the way that entities are represented in
the DOM?</q>
@@ -159,65 +160,31 @@
node containing the entity expansion as text.</p>
</a>
</faq>
- <faq title="Non-Validating">
- <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
+
+ <faq title="Why does "non-validating" not mean "well-formedness checking only"?">
+ <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
requires of the parser, including entity substitution, defaulting of
attribute values, and attribute normalization.</p>
- <p>This table describes what "non-validating" really means for &javaparsername; parsers.
+ <p>This table describes what "non-validating" really means for &javaparsername; parsers.
In this table, "no DTD" means no internal or external DTD subset is present.</p>
<table>
<tr><tn/>
<th colspan="2">non-validating parsers</th>
<th colspan="2">validating parsers</th>
- </tr>
- <tr>
- <tn/>
- <th>DTD present</th>
- <th>no DTD</th>
- <th>DTD present</th>
- <th>no DTD</th>
- </tr>
- <tr>
- <th>DTD is read</th>
- <td>Yes</td>
- <td>No</td>
- <td>Yes</td>
- <td>Error</td>
- </tr>
- <tr>
- <th>entity substitution</th>
- <td>Yes</td>
- <td>No</td>
- <td>Yest</td>
- <td>Error</td>
- </tr>
- <tr>
- <th>defaulting of attributes</th>
- <td>Yes</td>
- <td>No</td>
- <td>Yes</td>
- <td>Error</td>
- </tr>
- <tr>
- <th>attribute normalization</th>
- <td>Yes</td>
- <td>No</td>
- <td>Yes</td>
- <td>Error</td>
- </tr>
- <tr>
- <th>checking against model</th>
- <td>No</td>
- <td>No</td>
- <td>Yes</td>
- <td>Error</td>
</tr>
+ <tr><tn/> <th>DTD present</th> <th>no DTD</th> <th>DTD present</th> <th>no DTD</th></tr>
+ <tr><th>DTD is read</th> <td>Yes</td> <td>No</td> <td>Yes</td> <td>Error</td></tr>
+ <tr><th>entity substitution</th> <td>Yes</td> <td>No</td> <td>Yest</td> <td>Error</td></tr>
+ <tr><th>defaulting of attributes</th> <td>Yes</td> <td>No</td> <td>Yes</td> <td>Error</td></tr>
+ <tr><th>attribute normalization</th> <td>Yes</td> <td>No</td> <td>Yes</td> <td>Error</td></tr>
+ <tr><th>checking against model</th> <td>No</td> <td>No</td> <td>Yes</td> <td>Error</td></tr>
</table>
</a>
</faq>
+
<faq title="Associating Data with a Node">
<q>How do associate my own data with a node in the DOM tree?</q>
<a><p>The class <code>org.apache.xerces.dom.NodeImpl</code> provides a
@@ -225,6 +192,7 @@
method that you can use to attach any object to a node in the DOM tree.</p>
</a>
</faq>
+
<faq title="Parsing Several Documents">
<q>How do I more efficiently parse several documents sharing a common DTD?</q>
<a> <p>DTDs are not currently cached by the parser. The common DTD, since it is
@@ -243,6 +211,7 @@
</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
1.4 +149 -103 xml-xerces/java/docs/features.xml
Index: features.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/features.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- features.xml 2000/01/07 23:32:28 1.3
+++ features.xml 2000/01/24 23:43:48 1.4
@@ -8,154 +8,200 @@
org.apache.xerces.parsers.DOMParser, you should use the SAX2 Configurable
interface (org.xml.sax.Configurable).</p>
<p>For example, to turn on the validation feature, do:</p>
- <source>
-SAXParser p=new SAXParser();
+<source>SAXParser p=new SAXParser();
try {
p.setFeature("http://xml.org/sax/features/validation",true);
} catch (SAXException e) {
System.out.println("error in setting up parser feature");
-}
- </source>
-
+}</source>
</s2>
+
<s2 title="General Features">
- <p>http://xml.org/sax/features/validation </p>
+ <anchor name="validation"/>
+ <p>http://xml.org/sax/features/validation</p>
<table>
- <tr><th>true</th><td>Validate the document.</td></tr>
- <tr><th>false</th><td>Do not validate the document.</td></tr>
- <tr><th>Default</th><td>false</td></tr>
- <tr><th>Note</th>
- <td>If this feature is set to true, the document must specify a grammar.
- If this feature is set to false, the document may specify a grammar
- and that grammar will be parsed but no validation of the document
- contents will be performed.</td></tr>
- <tr><th>See</th>
- <td>http://apache.org/xml/features/validation/dynamic
- <br/>http://xml.org/sax/features/namespaces</td></tr>
+ <tr><th>True:</th> <td>Validate the document.</td></tr>
+ <tr><th>False:</th> <td>Do not validate the document.</td></tr>
+ <tr><th>Default:</th> <td>false</td></tr>
+ <tr><th>Note:</th> <td>If this feature is set to true, the document must specify a grammar.
+ If this feature is set to false, the document may specify a grammar
+ and that grammar will be parsed but no validation of the document
+ contents will be performed.</td></tr>
+ <tr><th>See:</th> <td><link anchor="dynamic">http://apache.org/xml/features/validation/dynamic</link>
+ <br/><link anchor="namespaces">http://xml.org/sax/features/namespaces</link></td></tr>
</table>
+
+ <anchor name="external-general-entities"/>
<p>http://xml.org/sax/features/external-general-entities</p>
<table>
- <tr><th>true</th><td>Include external general (text) entities.</td></tr>
- <tr><th>false</th><td>Do not include external general entities.</td></tr>
- <tr><th>Default</th><td>true</td></tr>
- <tr><th>See</th>
- <td>http://xml.org/sax/features/external-parameter-entities</td></tr>
+ <tr><th>True:</th> <td>Include external general (text) entities.</td></tr>
+ <tr><th>False:</th> <td>Do not include external general entities.</td></tr>
+ <tr><th>Default:</th> <td>true</td></tr>
+ <tr><th>See:</th>
+ <td><link anchor="external-parameter-entities">http://xml.org/sax/features/external-parameter-entities</link></td></tr>
</table>
+
+ <anchor name="external-parameter-entities"/>
<p>http://xml.org/sax/features/external-parameter-entities</p>
<table>
- <tr><th>true</th><td>Include external parameter entities and the external DTD subset.</td></tr>
- <tr><th>false</th><td>Do not include external parameter entities or the external DTD subset.</td></tr>
- <tr><th>Default</th><td>true</td></tr>
- <tr><th>See</th>
- <td>http://xml.org/sax/features/external-parameter-entities</td></tr>
+ <tr><th>True:</th> <td>Include external parameter entities and the external DTD subset.</td></tr>
+ <tr><th>False:</th> <td>Do not include external parameter entities or the external DTD subset.</td></tr>
+ <tr><th>Default:</th> <td>true</td></tr>
+ <tr><th>See:</th>
+ <td><link anchor="external-parameter-entities">http://xml.org/sax/features/external-parameter-entities</link></td></tr>
</table>
+
+ <anchor name="namespaces"/>
<p>http://xml.org/sax/features/namespaces</p>
<table>
- <tr><th>true</th><td>Perform namespace processing: prefixes will be stripped off element and
- attribute names and replaced with the corresponding namespace URIs. By
- default, the two will simply be concatenated, but the namespace-sep core
- property allows the application to specify a delimiter string for
- separating the URI part and the local part.</td></tr>
- <tr><th>false</th><td>Do not perform namespace processing.</td></tr>
- <tr><th>Default</th><td>false</td></tr>
- <tr><th>Note</th><td>If the validation feature is set to true, then the document must contain
- a grammar that supports the use of namespaces.</td></tr>
- <tr><th>See</th>
- <td>http://xml.org/sax/features/validation
- <br/>http://xml.org/sax/properties/namespace-sep</td></tr>
+ <tr><th>True:</th> <td>Perform namespace processing: prefixes will be stripped off element and
+ attribute names and replaced with the corresponding namespace URIs. By
+ default, the two will simply be concatenated, but the namespace-sep core
+ property allows the application to specify a delimiter string for
+ separating the URI part and the local part.</td></tr>
+ <tr><th>False:</th> <td>Do not perform namespace processing.</td></tr>
+ <tr><th>Default:</th> <td>false</td></tr>
+ <tr><th>Note:</th> <td>If the validation feature is set to true, then the document must contain
+ a grammar that supports the use of namespaces.</td></tr>
+ <tr><th>See:</th> <td><link anchor="validation">http://xml.org/sax/features/validation</link>
+ <br/><link idref="properties" anchor="namespace-sep">http://xml.org/sax/properties/namespace-sep</link></td></tr>
</table>
- <p>http://xml.org/sax/features/use-locator</p>
- <table>
- <tr><th>true</th><td>Provide a Locator using the DocumentHandler setDocumentLocator callback.</td></tr>
- <tr><th>false</th><td>Explicitly allow the parser not to provide a Locator (but it still may).</td></tr>
- <tr><th>Default</th><td>true</td></tr>
- <tr><th>Note</th><td>&javaparsername; always provides a Locator to the document handler.</td></tr>
- </table>
+
+ <anchor name="dynamic"/>
<p>http://apache.org/xml/features/validation/dynamic</p>
<table>
- <tr><th>true</th><td>The parser will validate the document only if a grammar is specified.</td></tr>
- <tr><th>false</th><td>Validation is determined by the state of the
- http://xml.org/sax/features/validation feature.</td></tr>
- <tr><th>Default</th><td>false</td></tr>
- <tr><th>See</th><td>http://xml.org/sax/features/validation</td></tr>
+ <tr><th>True:</th> <td>The parser will validate the document only if a grammar is specified.</td></tr>
+ <tr><th>False:</th> <td>Validation is determined by the state of the
+ <link anchor="validation">http://xml.org/sax/features/validation</link> feature.</td></tr>
+ <tr><th>Default:</th> <td>false</td></tr>
+ <tr><th>See:</th> <td><link anchor="validation">http://xml.org/sax/features/validation</link></td></tr>
</table>
+
+ <anchor name="warn-on-duplicate-attdef"/>
<p>http://apache.org/xml/features/validation/warn-on-duplicate-attdef</p>
<table>
- <tr><th>true</th><td>Warn on duplicate attribute declaration.</td></tr>
- <tr><th>false</th><td>Do not warn on duplicate attribute declaration.</td></tr>
- <tr><th>Default</th><td>true</td></tr>
+ <tr><th>True:</th><td>Warn on duplicate attribute declaration.</td></tr>
+ <tr><th>False:</th><td>Do not warn on duplicate attribute declaration.</td></tr>
+ <tr><th>Default:</th><td>true</td></tr>
</table>
+
+ <anchor name="warn-on-undeclared-elemdef"/>
<p>http://apache.org/xml/features/validation/warn-on-undeclared-elemdef</p>
<table>
- <tr><th>true</th><td>Warn if element referenced in content model is not declared.</td></tr>
- <tr><th>false</th><td>Do not warn if element referenced in content model is not declared.</td></tr>
- <tr><th>Default</th><td>true</td></tr>
+ <tr><th>True:</th> <td>Warn if element referenced in content model is not declared.</td></tr>
+ <tr><th>False:</th> <td>Do not warn if element referenced in content model is not declared.</td></tr>
+ <tr><th>Default:</th> <td>true</td></tr>
</table>
+
+ <anchor name="allow-java-encodings"/>
<p>http://apache.org/xml/features/allow-java-encodings</p>
<table>
- <tr><th>true</th><td>Allow Java encoding names in XMLDecl and TextDecl line.</td></tr>
- <tr><th>false</th><td>Do not allow Java encoding names in XMLDecl and TextDecl line.</td></tr>
- <tr><th>Default</th><td>false</td></tr>
- <tr><th>Note</th><td>A true value for this feature allows the encoding of the file to be
- specified as a Java encoding name as well as the standard ISO encoding
- name. Be aware that other parsers may not be able to use Java encoding
- names. If this feature is set to false, an error will be generated if
- Java encoding names are used.</td></tr>
+ <tr><th>True:</th> <td>Allow Java encoding names in XMLDecl and TextDecl line.</td></tr>
+ <tr><th>False:</th> <td>Do not allow Java encoding names in XMLDecl and TextDecl line.</td></tr>
+ <tr><th>Default:</th> <td>false</td></tr>
+ <tr><th>Note:</th> <td>A true value for this feature allows the encoding of the file to be
+ specified as a Java encoding name as well as the standard ISO encoding
+ name. Be aware that other parsers may not be able to use Java encoding
+ names. If this feature is set to false, an error will be generated if
+ Java encoding names are used.</td></tr>
</table>
+
+ <anchor name="continue-after-fatal-error"/>
<p>http://apache.org/xml/features/continue-after-fatal-error</p>
<table>
- <tr><th>true</th><td>Continue after fatal error.</td></tr>
- <tr><th>false</th><td>Stops parse on first fatal error.</td></tr>
- <tr><th>Default</th><td>false</td></tr>
+ <tr><th>True:</th><td>Continue after fatal error.</td></tr>
+ <tr><th>False:</th><td>Stops parse on first fatal error.</td></tr>
+ <tr><th>Default:</th><td>false</td></tr>
</table>
</s2>
<s2 title="DOM Features">
+ <anchor name="defer-node-expansion"/>
<p>http://apache.org/xml/features/dom/defer-node-expansion</p>
<table>
- <tr><th>true</th><td>Lazy DOM node expansion.</td></tr>
- <tr><th>false</th><td>Full DOM node expansion.</td></tr>
- <tr><th>Default</th><td>true</td></tr>
- <tr><th>Note</th><td>This feature only applies when the
- http://apache.org/xml/properties/dom/document-class-name property is
- set to a value other than the name of the default document factory.
- If this feature is set to true, the DOM nodes in the returned
- document are expanded as the tree is traversed. This feature allows
- the parser to return a document faster than if the tree is fully
- expanded during parsing and improves memory usage when the whole
- tree is not traversed.</td></tr>
- <tr><th>See</th><td>http://apache.org/xml/properties/dom/document-class-name</td></tr>
+ <tr><th>True:</th> <td>Lazy DOM node expansion.</td></tr>
+ <tr><th>False:</th> <td>Full DOM node expansion.</td></tr>
+ <tr><th>Default:</th> <td>true</td></tr>
+ <tr><th>Note:</th> <td>This feature only applies when the
+ <link idref="properties" anchor="document-class-name">http://apache.org/xml/properties/dom/document-class-name</link> property is
+ set to a value other than the name of the default document factory.
+ If this feature is set to true, the DOM nodes in the returned
+ document are expanded as the tree is traversed. This feature allows
+ the parser to return a document faster than if the tree is fully
+ expanded during parsing and improves memory usage when the whole
+ tree is not traversed.</td></tr>
+ <tr><th>See</th> <td><link idref="properties" anchor="document-class-name">http://apache.org/xml/properties/dom/document-class-name</link></td></tr>
</table>
+
+ <anchor name="create-entity-ref-nodes"/>
<p>http://apache.org/xml/features/dom/create-entity-ref-nodes</p>
<table>
- <tr><th>true</th><td>Create EntityReference nodes in the DOM tree.</td></tr>
- <tr><th>false</th><td>Do not create EntityReference nodes in the DOM tree.</td></tr>
- <tr><th>Default</th><td>true</td></tr>
- <tr><th>Note</th><td>This feature only affects the appearance of EntityReference nodes in
- the DOM tree. The document will always contain the entity reference
- child nodes.</td></tr>
+ <tr><th>True:</th> <td>Create EntityReference nodes in the DOM tree.</td></tr>
+ <tr><th>False:</th> <td>Do not create EntityReference nodes in the DOM tree.</td></tr>
+ <tr><th>Default:</th> <td>true</td></tr>
+ <tr><th>Note:</th> <td>This feature only affects the appearance of EntityReference nodes in
+ the DOM tree. The document will always contain the entity reference
+ child nodes.</td></tr>
+ </table>
+
+ <anchor name="include-ignorable-whitespace"/>
+ <p>http://apache.org/xml/features/dom/include-ignorable-whitespace</p>
+ <table>
+ <tr><th>True:</th> <td>Includes text nodes that can be
+ considered "ignorable whitespace" in the DOM tree.</td></tr>
+ <tr><th>False:</th> <td>Does not include ignorable whitespace in the DOM tree.</td></tr>
+ <tr><th>Default:</th> <td>true</td></tr>
+ <tr><th>Note:</th> <td>The only way that the parser can determine if text is ignorable is
+ by reading the associated grammar and having a content model for
+ the document. When ignorable whitespace text nodes are included in
+ the DOM tree, they will be flagged as ignorable. The ignorable flag
+ can be queried by calling the TextImpl#isIgnorableWhitespace():boolean
+ method.</td></tr>
+ </table>
+
+ <anchor name="grammar-access"/>
+ <p>http://apache.org/xml/features/domx/grammar-access</p>
+ <table>
+ <tr><th>True:</th> <td>Creates nodes that describe the grammar in the DOM tree.</td></tr>
+ <tr><th>False:</th> <td>Does not create create grammar access nodes in the DOM
+ tree. This setting makes the DOM behave as a standard
+ DOM Level 1 implementation.</td></tr>
+ <tr><th>Note:</th> <td>The grammar access nodes are appended as children of the
+ DocumentType node. The grammar is specified as an
+ XML Schema document tree, whether it was read from a
+ document with an associated DTD or XML Schema grammar.
+ This is currently a violation of the DOM Level 1
+ specification.
+ <br/><em>**** This is an experimental feature that is not guaranteed </em>
+ <br/><em>**** to be supported in future versions of
+ the parser.</em></td></tr>
</table>
- <p>http://apache.org/xml/features/dom/include-ignorable-whitespace</p>
- <table>
- <tr><th>true</th><td>Include ignorable whitespace text nodes in the DOM tree.</td></tr>
- <tr><th>false</th><td>Do not include ignorable whitespace text nodes in the DOM tree.</td></tr>
- <tr><th>Default</th><td>true</td></tr>
- <tr><th>Note</th><td>The only way that the parser can determine if text
- is ignorable is by reading the associated grammar
- and having a content model for the document. When
- ignorable whitespace text nodes are included in
- the DOM tree, they will be flagged as ignorable.
- The ignorable flag can be queried by calling the
- TextImpl#isIgnorableWhitespace():boolean method.</td></tr>
- </table>
</s2>
<s2 title="SAX Features">
+ <anchor name="use-locator"/>
<p>http://xml.org/sax/features/use-locator</p>
<table>
- <tr><th>true</th><td>Provide a Locator using the DocumentHandler setDocumentLocator callback.</td></tr>
- <tr><th>false</th><td>Explicitly allow the parser not to provide a Locator (but it still may).</td></tr>
- <tr><th>Default</th><td>true</td></tr>
- <tr><th>Note</th><td>&javaparsername; always provides a Locator to the document handler</td></tr>
+ <tr><th>True:</th> <td>Provide a Locator using the DocumentHandler setDocumentLocator callback.</td></tr>
+ <tr><th>False:</th> <td>Explicitly allow the parser not to provide a Locator (but it still may).</td></tr>
+ <tr><th>Default:</th> <td>true</td></tr>
+ <tr><th>Note:</th> <td>Xerces-J always provides a Locator to the document handler</td></tr>
+ </table>
+
+ <anchor name="normalize-text"/>
+ <p>http://xml.org/sax/features/normalize-text</p>
+ <table>
+ <tr><th>True:</th> <td>Ensure that all consecutive text is returned
+ in a single callback to the DocumentHandler
+ characters method.</td></tr>
+ <tr><th>False:</th> <td>Explicitly allow the parser to split
+ consecutive text into more than one callback
+ (but it still may not do so).</td></tr>
+ <tr><th>Default:</th> <td>true</td></tr>
+ <tr><th>Note:</th> <td>Xerces-J currently does not support allowing
+ consecutive text to be buffered and returned
+ in a single callback to the DocumentHandler
+ characters method.</td></tr>
</table>
+
</s2>
</s1>
1.2 +72 -112 xml-xerces/java/docs/properties.xml
Index: properties.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/properties.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- properties.xml 1999/12/18 00:17:11 1.1
+++ properties.xml 2000/01/24 23:43:48 1.2
@@ -2,149 +2,109 @@
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
<s1 title="Properties">
- <s2 title="Seting Features">
+ <s2 title="Setting Features">
<anchor name="properties"/>
<p>To set a property on either org.apache.xerces.parsers.SAXParser
or org.apache.xerces.parsers.DOMParser, you should use the SAX2
Configurable interface (org.xml.sax.Configurable).</p>
- <source>
-DOMParser p=new DOMParser();
+<source>DOMParser p=new DOMParser();
try {
p.setProperty("http://xml.org/sax/properties/namespace-sep","|");
} catch (SAXException e) {
System.out.println("error in setting up parser property");
-}
- </source>
+}</source>
</s2>
+
<s2 title="General Properties">
+ <anchor name="namespace-sep"/>
<p>http://xml.org/sax/properties/namespace-sep</p>
<table>
- <tr>
- <th>Type:</th>
- <td>java.lang.String</td>
- </tr>
- <tr>
- <th>Access:</th>
- <td>read-write</td>
- </tr>
- <tr>
- <th>Desc:</th>
- <td>The separator string that will appear between the namespace
- URI and the local part of the name when namespace processing is being
- performed. If the value is the empty string, the two parts will be
- concatenated. </td>
- </tr>
- <tr>
- <th>Default:</th>
- <td>""</td>
- </tr>
- <tr>
- <th>See:</th>
- <td>http://xml.org/sax/features/namespaces</td>
- </tr>
+ <tr><th>Type:</th> <td>java.lang.String</td></tr>
+ <tr><th>Access:</th> <td>read-write</td></tr>
+ <tr><th>Desc:</th> <td>The separator string that will appear between the namespace
+ URI and the local part of the name when namespace processing is being
+ performed. If the value is the empty string, the two parts will be
+ concatenated. </td></tr>
+ <tr><th> Default: </th> <td>""</td></tr>
+ <tr><th>See:</th> <td><link idref="features" anchor="namespaces">http://xml.org/sax/features/namespaces</link></td></tr>
+ </table>
+
+ <anchor name="xml-string"/>
+ <p>http://xml.org/sax/properties/xml-string</p>
+ <table>
+ <tr><th>Type:</th> <td>java.lang.String</td></tr>
+ <tr><th>Access:</th> <td>read-only</td></tr>
+ <tr><th>Desc:</th> <td>Get the string of characters associated with the current event. If the
+ parser recognizes and supports this property but is not currently
+ parsing text, it should return null.</td></tr>
+ <tr><th>Note:</th> <td>This property is currently not supported because the contents of the
+ XML string returned by this property is not well defined.</td></tr>
</table>
</s2>
+
<s2 title="DOM Parser Properties">
+ <anchor name="current-element-node"/>
<p>http://apache.org/xml/properties/dom/current-element-node</p>
<table>
- <tr>
- <th>Type:</th>
- <td>org.w3c.dom.Node</td>
- </tr>
- <tr>
- <th>Access:</th>
- <td>read-only</td>
- </tr>
- <tr>
- <th>Desc:</th>
- <td>The current DOM element node while parsing.</td>
- </tr>
- <tr>
- <th>Note:</th>
- <td>This property is useful for determining the location
- with a DOM document when an error occurs.</td>
- </tr>
- <tr>
- <th>See:</th>
- <td>http://xml.org/sax/properties/dom-node</td>
- </tr>
+ <tr><th>Type:</th> <td>org.w3c.dom.Node</td></tr>
+ <tr><th>Access:</th> <td>read-only</td></tr>
+ <tr><th>Desc:</th> <td>The current DOM element node while parsing.</td></tr>
+ <tr><th>Note:</th> <td>This property is useful for determining the location
+ with a DOM document when an error occurs.</td></tr>
+ <tr><th>See:</th> <td><link anchor="dom-node">http://xml.org/sax/properties/dom-node</link></td></tr>
</table>
+
+ <anchor name="document-class-name"/>
<p>http://apache.org/xml/properties/dom/document-class-name</p>
<table>
- <tr>
- <th>Type:</th>
- <td>java.lang.String</td>
- </tr>
- <tr>
- <th>Access:</th>
- <td>read-write</td>
- </tr>
- <tr>
- <th>Desc:</th>
- <td>The fully qualified class name of the DOM implementation.
- The implementation used must have a zero argument constructor.</td>
- </tr>
- <tr>
- <th>Default:</th>
- <td>"org.apache.xerces.dom.DocumentImpl"</td>
- </tr>
- <tr>
- <th>Note:</th>
- <td>When the document class name is set to a value other
- than the name of the default document factory, the
- deferred node expansion feature does not work. </td>
- </tr>
- <tr>
- <th>See:</th>
- <td>http://apache.org/xml/features/dom/defer-node-expansion</td>
- </tr>
+ <tr><th>Type:</th> <td>java.lang.String</td></tr>
+ <tr><th>Access:</th> <td>read-write</td></tr>
+ <tr><th>Desc:</th> <td>The fully qualified class name of the DOM
+ implementation. The implementation used must
+ have a zero argument constructor.</td></tr>
+ <tr><th>Default:</th> <td>"org.apache.xerces.dom.DocumentImpl"</td></tr>
+ <tr><th>Note:</th> <td>When the document class name is set to a value other
+ than the name of the default document factory, the
+ deferred node expansion feature does not work. </td></tr>
+ <tr><th>See:</th> <td><link idref="features" anchor="defer-node-expansion">http://apache.org/xml/features/dom/defer-node-expansion</link></td></tr>
</table>
</s2>
+
<s2 title="SAX Parser Properties">
+ <anchor name="DeclHandler"/>
<p>http://xml.org/sax/handlers/DeclHandler</p>
<table>
- <tr>
- <th>Type:</th>
- <td>org.xml.sax.misc.DeclHandler</td>
- </tr>
- <tr>
- <th>Access:</th>
- <td>read-write</td>
- </tr>
- <tr>
- <th>Desc:</th>
- <td>Set the handler for DTD declarations.</td>
- </tr>
+ <tr><th>Type:</th> <td>org.xml.sax.misc.DeclHandler</td></tr>
+ <tr><th>Access:</th> <td>read-write</td></tr>
+ <tr><th>Desc:</th> <td>Set the handler for DTD declarations.</td></tr>
</table>
+
+ <anchor name="LexicalHandler"/>
<p>http://xml.org/sax/handlers/LexicalHandler</p>
<table>
- <tr>
- <th>Type:</th>
- <td>org.xml.sax.misc.LexicalHandler</td>
- </tr>
- <tr>
- <th>Access:</th>
- <td>read-write</td>
- </tr>
- <tr>
- <th>Desc:</th>
- <td>Set the handler for lexical parsing events.</td>
- </tr>
+ <tr><th>Type:</th> <td>org.xml.sax.misc.LexicalHandler</td></tr>
+ <tr><th>Access:</th> <td>read-write</td></tr>
+ <tr><th>Desc:</th> <td>Set the handler for lexical parsing events.</td></tr>
</table>
+
+ <anchor name="NamespaceHandler"/>
<p>http://xml.org/sax/handlers/NamespaceHandler</p>
<table>
- <tr>
- <th>Type:</th>
- <td>org.xml.sax.misc.NamespaceHandler</td>
- </tr>
- <tr>
- <th>Access:</th>
- <td>read-write</td>
- </tr>
- <tr>
- <th>Desc:</th>
- <td>Set the handler for lexical parsing events.</td>
- </tr>
+ <tr><th>Type:</th> <td>org.xml.sax.misc.NamespaceHandler</td></tr>
+ <tr><th>Access:</th> <td>read-write</td></tr>
+ <tr><th>Desc:</th> <td>Set the handler for lexical parsing events.</td></tr>
+ </table>
+
+ <anchor name="dom-node"/>
+ <p>http://xml.org/sax/properties/dom-node</p>
+ <table>
+ <tr><th>Type:</th> <td>org.w3c.dom.Node</td></tr>
+ <tr><th>Access:</th> <td>read-only</td></tr>
+ <tr><th>Desc:</th> <td>The DOM node currently being visited,
+ if SAX is being used as a DOM iterator.
+ If the parser recognizes and supports this property but is
+ not currently visiting a DOM node, it should return null.</td></tr>
</table>
+
</s2>
</s1>
1.2 +12 -14 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.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sam-iterator.xml 1999/12/18 00:17:11 1.1
+++ sam-iterator.xml 2000/01/24 23:43:48 1.2
@@ -3,11 +3,11 @@
<s1 title="IteratorView Sample">
<s2 title="IteratorView">
- <p>The IteratorView 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 IteratorView uses an example filter, NameNodeFilter, 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 DOMTreeFull class that displays the full DOM tree with all
the nodes.</p>
@@ -17,32 +17,32 @@
<s3 title="Iterator Group">
<ul>
- <li>Next - calls the next() functions and selects the next node in the tree.</li>
- <li>Previous - calls the previous() function a and selects the previous node in
+ <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
the tree.</li>
</ul>
</s3>
<s3 title="Selected Node Group">
<ul>
- <li>remove - remove the selected Node and update the DOM tree. You
+ <li><code>remove</code> - remove the selected Node and update the DOM tree. You
must press an iterator button to see next or previous node selection. </li>
- <li>add - add a text node, to see the results of adding a node on the iterator.
+ <li><code>add</code> - add a text node, to see the results of adding a node on the iterator.
position. Again you must first press next or previous </li>
</ul>
</s3>
<s3 title="Iterator Settings Group">
<ul>
- <li>createNodeIterator - calls the factory method to create a new iterator
- with the corresponding whatToShow and NodenameFilter settings.</li>
+ <li><code>createNodeIterator</code> - calls the factory method to create a new iterator
+ with the corresponding <code>whatToShow</code> and <code>NameNodeFilter</code> settings.</li>
<ul>
<li>The root is set to be the root of the document, so it
starts at the top level each time.</li>
</ul>
- <li>whatToShow - you can singly or multiply select values and the
+ <li><code>whatToShow</code> - you can singly or multiply select values and the
iterator is constrained to showing these types.</li>
- <li>NodeNameFilter - An empty string is converted to null and given
- to the NodeNameFilter class.</li>
+ <li><code>NodeNameFilter</code> - An empty string is converted to null and given
+ to the <code>NodeNameFilter</code> class.</li>
<ul>
<li>An empty string matches all nodes.</li>
<li>A non-empty string is forced to match node names.</li>
@@ -52,8 +52,6 @@
</s3>
</s2>
<s2 title="Running IteratorView">
- <source>
- java dom.traversal.IteratorView <fileName>
- </source>
+<source>java dom.traversal.IteratorView <fileName></source>
</s2>
</s1>
1.2 +29 -25 xml-xerces/java/docs/sam-tree.xml
Index: sam-tree.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/sam-tree.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sam-tree.xml 1999/12/18 00:17:11 1.1
+++ sam-tree.xml 2000/01/24 23:43:48 1.2
@@ -3,56 +3,60 @@
<s1 title="TreeWalker Sample">
<s2 title="TreeWalker">
- <p>The TreeWalkerviewView is an interactive UI sample that displays the DOM
+ <p>The <code>TreeWalkerviewView</code> 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 TreeWalkerviewView uses an example filter, NameNodeFilter, that can be
- controlled from the UI and a DOMTreeFull class that displays the full DOM tree
+ <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>The controls are called through to to the corresponding TreeWalker function. If
- you are familiar with the DOM Level 2 Traversal specification, these controls are
+ <p>The controls are called through to to the corresponding
+ <code>TreeWalker</code> function. If you are familiar with the DOM
+ Level 2 Traversal specification, these controls are
fairly easy to understand.</p>
<s3 title="Document Order Traversal Group">
<ul>
- <li>Next - calls the next() functions and selects the next in the tree.</li>
- <li>Previous - calls the previous() function a and selects the previous node in
- the DOM tree.</li>
+ <li>Next - calls the <code>next()</code> functions and selects
+ the next in the tree.</li>
+ <li>Previous - calls the <code>previous()</code> function a and
+ selects the previous node in the DOM tree.</li>
</ul>
</s3>
<s3 title="Walk Group">
- <p>Parent, Previous Sibling, Next Sibling, First Child, Last Child - call the
- corresponding function in TreeWalker and show the result as a selected Node.</p>
+ <p>Parent, Previous Sibling, Next Sibling, First Child, Last Child - call the
+ corresponding function in TreeWalker and show the result as a selected Node.</p>
</s3>
<s3 title="Selected Node Group">
<ul>
<li>current - set the current node to the selected node.</li>
<li>remove - remove the selected node and update the tree.
- You must press a button to see next or previous node selection.</li>
+ You must press a button to see next or previous node selection.</li>
<li>add - add a text node.
- You must press a button to see next or previous node selection.</li>
+ You must press a button to see next or previous node selection.</li>
</ul>
</s3>
<s3 title="Filter Settings Group">
<ul>
- <li>createNodeTreeWalker - calls the factory method to create a new
- TreeWalker with the corresponding whatToShow and NodenameFilter
+ <li><code>createNodeTreeWalker</code> - calls the factory
+ method to create a new <code>TreeWalker</code> with the
+ corresponding <code>whatToShow</code> and <code>NodenameFilter</code>
settings. The selected node becomes the TreeWalker root.</li>
- <li>whatToShow - you can singly or multiply select these values by pressing
- the control key and the TreeWalker is constrained to these types.</li>
- <li>NodeNameFilter - an empty string is converted to null and given to the
- NodeNameFilter example filter class provided.</li>
- <ul>
- <li>An empty string (null) matches ALL nodes.</li>
- <li>A non-empty string is forced to match node names.</li>
- </ul>
+ <li><code>whatToShow</code> - you can singly or multiply select
+ these values by pressing the control key and the
+ <code>TreeWalker</code> is constrained to these types.</li>
+ <li><code>NodeNameFilter</code> - an empty string is
+ converted to null and given to the
+ <code>NodeNameFilter</code> example filter class provided.</li>
+ <ul>
+ <li>An empty string (null) matches ALL nodes.</li>
+ <li>A non-empty string is forced to match node names.</li>
+ </ul>
</ul>
</s3>
</s2>
<s2 title="Running TreeWalker">
- <source>
- java dom.traversal.TreeWalkerView <fileName>
- </source>
+<source>java dom.traversal.TreeWalkerView <fileName></source>
</s2>
</s1>
1.4 +16 -14 xml-xerces/java/docs/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/samples.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- samples.xml 2000/01/21 00:33:35 1.3
+++ samples.xml 2000/01/24 23:43:48 1.4
@@ -17,38 +17,40 @@
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
- correctly installed JDK. If you do not already have a JDK already on your computer download
- one from Sun's Java website: <jump href="http://java.sun.com">
- http://java.sun.com</jump> or from IBM's website
+ correctly installed JDK. If you do not already have a JDK already on
+ your computer download one from Sun's Java website:
+ <jump href="http://java.sun.com">http://java.sun.com</jump> or from
+ IBM's website
<jump href="http://www.ibm.com/developer/java/">http://www.ibm.com/developer/java/</jump>
- where you can find an "Enhanced Windows JDK" that is optimized for the Windows platform.
- The sample applications
+ where you can find an "Enhanced Windows JDK" that is optimized
+ for the Windows platform. The sample applications
described in the following pages support Java 1 - JDK 1.1.6. 1.1.7, 1.1.8 or
Java 2 - JDK 1.2.2. </note>
<note>UNIX: Command lines in the pages linked below use the Windows path
- separator ';' (semicolon) and directory separator '\' (backslash)..
- On UNIX, use the ':' (colon) character to separate the JAR files in the classpath,
- and replace Windows directory separator '\' (backslash) with '/' (forward slash).</note>
+ separator ';' (semicolon) and directory separator '\' (backslash)..
+ On UNIX, use the ':' (colon) character to separate the JAR files in the classpath,
+ and replace Windows directory separator '\' (backslash)
+ with '/' (forward slash).</note>
</s2>
<s2 title="IteratorView Sample">
- <p>The IteratorView 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 IteratorView uses an example filter, NameNodeFilter, 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><link idref="iterator">IteratorView page</link></p>
</s2>
<s2 title="TreeWalker Sample">
- <p>The TreeWalkerviewView is an interactive UI sample that displays the DOM
+ <p>The <code>TreeWalkerviewView</code> 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 TreeWalkerviewView uses an example filter, NameNodeFilter, that can be
- controlled from the UI and a DOMTreeFull class that displays the full DOM tree
+ <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>
</s2>
1.3 +3 -8 xml-xerces/java/docs/schema.xml
Index: schema.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/schema.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- schema.xml 1999/12/20 17:41:03 1.2
+++ schema.xml 2000/01/24 23:43:48 1.3
@@ -79,18 +79,13 @@
<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>
+</document></source>
<p>Another requirement is that the XML Schema document's grammar must
have a <!DOCTYPE ...> line specifying the DTD for XML Schema grammar.
The DOCTYPE must specify the following system identifier:<br/>
- <code>
-http://www.w3.org/XML/Group/1999/09/23-xmlschema/structures/structures.dtd
- </code>
- </p>
+ <code>http://www.w3.org/XML/Group/1999/09/23-xmlschema/structures/structures.dtd</code></p>
<p>Also, there must be an attribute declaration for the xmlns attribute
used to find the schema (document in the example above).</p>
<p>Review the sample file, "data/personal.xsd" for an example of an XML
1.2 +22 -21 xml-xerces/java/docs/y2k.xml
Index: y2k.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/y2k.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- y2k.xml 1999/12/18 00:17:11 1.1
+++ y2k.xml 2000/01/24 23:43:48 1.2
@@ -5,24 +5,26 @@
<s2 title="Apache Xerces Parser Year-2000 Readiness">
<p>Q: Are the Xerces parsers Year-2000-compliant? </p>
<p>Yes, Xerces-J and Xerces-C are Year 2000 compliant.
-They do not currently use any dates at all (at least until the XML Schema date datatypes
-are fully supported). However, you may still have Y2K problems if the underlying OS or Java implementation has
-problems with dates past year 2000 (e.g. OS calls which accept or return year numbers).
-</p>
-<p>Most (UNIX) systems store dates internally as signed 32-bit integers which contain the number of seconds since 1st January 1970, so the magic boundary to worry about is the year 2038 and not 2000. But modern operating systems shouldn't cause any trouble at all.
-</p>
-
-<p>The Apache Xerces project is an open-source software product of the Apache Software Foundation.
-The project and the Foundation cannot and does not offer legal assurances regarding any
-suitability of the software for your application. There are several commercial
-support organizations and derivative products available that may be able to certify the
-software and provide you with any assurances you may require (IBM's Websphere product is one of them).
-</p>
-<p>The Apache HTTP server software is distributed with the following
-disclaimer, found in the software license:
-</p>
-<source>
-THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+ They do not currently use any dates at all (at least until the XML
+ Schema date datatypes are fully supported). However, you may still
+ have Y2K problems if the underlying OS or Java implementation has
+ problems with dates past year 2000 (e.g. OS calls which accept or
+ return year numbers).</p>
+ <p>Most (UNIX) systems store dates internally as signed 32-bit
+ integers which contain the number of seconds since 1st January 1970,
+ so the magic boundary to worry about is the year 2038 and not 2000.
+ But modern operating systems shouldn't cause any trouble at all.</p>
+
+ <p>The Apache Xerces project is an open-source software product
+ of the Apache Software Foundation. The project and the Foundation
+ cannot and does not offer legal assurances regarding any suitability
+ of the software for your application. There are several commercial
+ support organizations and derivative products available that may be
+ able to certify the software and provide you with any assurances you
+ may require (IBM's Websphere product is one of them).</p>
+ <p>The Apache HTTP server software is distributed with the following
+ disclaimer, found in the software license: </p>
+<source>THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
@@ -33,7 +35,6 @@
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
- </source>
-</s2>
+SUCH DAMAGE.</source>
+ </s2>
</s1>