You are viewing a plain text version of this content. The canonical link for it is here.
Posted to crimson-cvs@xml.apache.org by ed...@apache.org on 2001/01/26 03:14:02 UTC
cvs commit: xml-crimson/docs relnotes.html readme.html install.html
edwingo 01/01/25 18:14:02
Modified: docs relnotes.html readme.html install.html
Log:
Update docs
Revision Changes Path
1.2 +129 -178 xml-crimson/docs/relnotes.html
Index: relnotes.html
===================================================================
RCS file: /home/cvs/xml-crimson/docs/relnotes.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- relnotes.html 2000/11/23 01:53:40 1.1
+++ relnotes.html 2001/01/26 02:14:02 1.2
@@ -1,11 +1,12 @@
-<HTML><HEAD>
- <!-- $Id: relnotes.html,v 1.1 2000/11/23 01:53:40 edwingo Exp $
+<html>
+ <head>
+ <!-- $Id: relnotes.html,v 1.2 2001/01/26 02:14:02 edwingo Exp $
-->
- <TITLE>
+ <title>
Java API for XML Processing -- Release Notes
- </TITLE>
- <STYLE>
+ </title>
+ <style>
<!--
BODY {
font-family: Lucida, Helvetica, Univers, sans-serif;
@@ -18,91 +19,35 @@
font-family: Courier, monospace;
}
-->
- </STYLE>
-</HEAD>
- <BODY BGCOLOR="#eeeeff">
-
-
-<H1>
-Java API for XML Processing<br>
-Release Notes
-</H1>
-<center>
-<b>Version:</b> 1.1ea<br>
-</center>
-
-<P>
-This document contains notes that may help you use this library
-more effectively.
-
-<P>
-<!--
-Please feel free to send problem reports,
-questions, and other feedback to the feedback alias,
-<a href="mailto:xml-feedback@java.sun.com">
-<xml-feedback@java.sun.com></a>.
-With respect to new feature requests, please keep in mind that we
-want to see packages built on top of this core for most features.
-The core API is intended to facilitate a layered architecture
-for value-added products that leverage XML.
--->
-
-<!--
-<H4> Conformance </H4>
-
-<UL>
- <LI> The parsers conform to the W3C's
- <a href=http://www.w3.org/TR/1998/REC-xml-19980210>XML 1.0</a>
- recommendation. Sun has done extensive testing to ensure that
- they conform as closely as possible to this recommendation.
-
- <LI> The parser supports the <a href=http://java.sun.com/xml>JAXP
- 1.0</a> pluggability API.
-
- <LI> The parse tree supports the XML (core) part of W3C's
- <a href=http://www.w3.org/TR/REC-DOM-Level-1/>DOM Level 1</a>
- recommendation.
-
- <LI> In combination, the two also support the current W3C
- <a href=http://www.w3.org/TR/REC-xml-names/>XML Namespaces</a>
- recommendation.
-
- <LI> The parser supports the <a href=http://www.megginson.com/SAX>SAX
- 1.0</a> API. Sun has done extensive testing to ensure that it conforms
- as closely as possible to this API.
-
- <LI> The entity resolution used within the parser normally
- conforms to the IETF's RFC 2376 registration for XML-related
- MIME content types. This can be overridden as required.
- (See below; overriding may be necessary because many web servers do
- not conform to that specification, and report incorrect character
- set encoding information.)
-
- <LI> This parser supports all of the character encodings supported
- by the Java platform with which it is used. See the package
- overview for the <em>com.sun.xml.parser</em> package for more
- detailed information, including names of specific encodings that
- are widely used.
-
- <LI> When used in a supported configuration (JDK 1.1.8 and later),
- this software is Y2K compliant; it has no date related content.
-
- </UL>
--->
- <h4> XSLT Support </h4>
+ </style>
+ </head>
+ <body bgcolor="#eeeeff">
+
+ <h1>Java<sup><font size="-2">TM</font></sup> API for XML Processing<br>
+ Release Notes
+ </h1>
+ <center>
+ <b>Version:</b> 1.1ea2 (Early Access 2)<br>
+ </center>
+
+ <p>This document contains notes that may help you use this library
+ more effectively.
+ <p>
+
+ <h4>XSLT Support</h4>
<ul>
<li><a href="http://www.w3.org/TR/1999/REC-xslt-19991116">XSLT</a> is
supported in this release via the
- <a href="docs/api/javax/xml/transform/TransformFactory.html">
- <code>javax.xml.transform.TransformFactory</code></a> class. See
+ <a href="docs/api/javax/xml/transform/package-summary.html">
+ <code>javax.xml.transform</code></a> package. See
the associated Javadoc for details on accessing basic functionality
in a XSLT processor independent manner. </li>
</ul>
-<H4> Parser </H4>
+ <h4>Parser</h4>
<ul>
- <li> There are two factory classes for making parsers pluggable. If
+ <li>There are two factory classes for making parsers pluggable. If
you write to the JAXP API in the
<a href="docs/api/javax/xml/parsers/package-summary.html">
<code>javax.xml.parsers</code></a>,
@@ -113,10 +58,11 @@
you can use the library in a manner independent of the underlying
implementing parser.</li>
- <li> To be notified of validation errors in an XML document, two
- things must happen.<ol>
+ <li>To be notified of validation errors in an XML document, these
+ items must be true:
+ <ol>
<li>Validation must be turned on. See the
- <code>setValidating</code> methods of
+ <code>setValidating</code> methods of
<a href="docs/api/javax/xml/parsers/DocumentBuilderFactory.html#setValidating(boolean)">
<code>javax.xml.parsers.DocumentBuilderFactory</code></a> or
<a href="docs/api/javax/xml/parsers/SAXParserFactory.html#setValidating(boolean)">
@@ -130,95 +76,91 @@
<a href="docs/api/org/xml/sax/XMLReader.html#setErrorHandler(org.xml.sax.ErrorHandler)">
<code>org.xml.sax.XMLReader</code></a>.
</li>
- </ol> The links provided above are only some of the ways to get
- notification of validation errors.
-
-<!--
- <LI> Please let us know about any diagnostics produced by the
- parser that are misleading or confusing.
--->
-
- <LI> Whenever you work with text encodings other than UTF-8 and
- UTF-16, you should put an encoding declaration at the very beginning of
- all your XML files (including DTDs). If you don't do this, the
- parser will not be able to determine the encoding being used, and
- will probably be unable to parse your document. A text declaration
- like <code><?xml version='1.0' encoding='euc-jp'?></code> says
- that the document uses the "euc-jp" encoding.
-
- <LI> The parser currently reports warnings, rather than errors,
- in cases where the declared and actual text encodings don't match.
- It may give those same warnings in the common case where the encoding
- name used internally to Java is not the one used in the document.
- If the declared encoding is truly an error, you'll usually see other
- errors (not warnings) being reported by the parser.
-
- <LI> The parser currently does not report an error for content
- models which are not deterministic. Accordingly it may not behave
- well when given data which matches an "ambiguous" content model
- such as <em>((a,b)|(a,c))</em>. DTDs with such models are in
- error, and must be restructured to be unambiguous. (In the example,
- <em>(a,(b|c))</em> is an equivalent legal content model.)
-
- <LI> If you are using JDK 1.1 with large numbers of symbols
- (more than can be counted in sixteen bits) you might encounter
- a message, <em>panic: 16-bit string hash table overflow</em>
- as the Java VM aborts. The Java 2 SDK does not have this limitation.
-
-
-</UL>
-
-<H4> Object Model </H4>
-
-<UL>
-
- <LI> Conforming to the XML specification, the parser reports all
- whitespace to the DOM even, if it's meaningless. Many applications
- do not want to see such whitespace. You can remove it by invoking
- the <em>Element.normalize</em> method, which merges adjacent text
- nodes and also canonicalizes adjacent whitespace into a single space
- (unless the <em>xml:space="preserve"</em> attribute prevents it).
-
- <LI> Currently, attribute nodes may not have children. Access their
- values as strings instead of enumerating children.
-
-
- <LI> Currently, when documents are cloned, the clone will not have a
- clone of the associated ElementFactory or DocumentType.
-
- <LI> The in-memory representation of text nodes has not been tuned
- to be efficient with respect to space utilization.
-
-</UL>
-
-<H4> Other Issues </H4>
+ </ol> See <a href="examples/index.html">example programs</a> for
+ more information. (The links provided above are only some of the
+ ways to get notification of validation errors.)
+ </li>
+ <li>Whenever you work with text encodings other than UTF-8 and
+ UTF-16, you should put an encoding declaration at the very
+ beginning of all your XML files (including DTDs). If you don't do
+ this, the parser will not be able to determine the encoding being
+ used, and will probably be unable to parse your document. A text
+ declaration like <code><?xml version='1.0'
+ encoding='euc-jp'?></code> says that the document uses the
+ "euc-jp" encoding.
+ </li>
+ <li>The parser currently reports warnings, rather than errors,
+ in cases where the declared and actual text encodings don't match.
+ It may give those same warnings in the common case where the
+ encoding name used internally to Java is not the one used in the
+ document. If the declared encoding is truly an error, you'll
+ usually see other errors (not warnings) being reported by the
+ parser.
+ </li>
+ <li>The parser currently does not report an error for content
+ models which are not deterministic. Accordingly it may not behave
+ well when given data which matches an "ambiguous" content model
+ such as <em>((a,b)|(a,c))</em>. DTDs with such models are in
+ error, and must be restructured to be unambiguous. (In the
+ example, <em>(a,(b|c))</em> is an equivalent legal content model.)
+ </li>
+ <li>If you are using JDK 1.1 with large numbers of symbols
+ (more than can be counted in sixteen bits) you might encounter a
+ message, <em>panic: 16-bit string hash table overflow</em> as the
+ Java VM aborts. The Java 2 SDK does not have this limitation.
+ </li>
+ </ul>
-<UL>
+ <h4>Object Model</h4>
- <LI> This software is a "Java Optional Package" for
- XML processing.
+ <ul>
+ <li>Conforming to the XML specification, the parser reports all
+ whitespace to the DOM even, if it's meaningless. Many applications
+ do not want to see such whitespace. You can remove it by invoking
+ the <em>Element.normalize</em> method, which merges adjacent text
+ nodes and also canonicalizes adjacent whitespace into a single
+ space (unless the <em>xml:space="preserve"</em> attribute prevents
+ it).
+ </li>
+ <li>Currently, attribute nodes do not have children. Access their
+ values as strings instead of enumerating children.
+ </li>
+ <li>Currently, when documents are cloned, the clone will not have a
+ clone of the associated ElementFactory or DocumentType.
+ </li>
+ <li>The in-memory representation of text nodes has not been tuned
+ to be efficient with respect to space utilization.
+ </li>
+ </ul>
- <LI> If you recompile the DOM implementation using versions of "javac"
- older than the Java 2 SDK version 1.2 you may run into a compiler bug.
- The symptom is a report of illegal access violations for some of the
- private classes inside the DOM implementation. This is because of
- incorrect code generated by the compiler. You should only compile
- these class files with a compiler that does not have this bug; you may
- also use the pre-compiled version in this release. There is no
- bytecode dependency on the Java 2 runtime; you may use these classes on
- JDK 1.1 systems also.
+ <h4>Other Issues</h4>
- <LI> The Microsoft SDK 3.2 for Java (and presumably all earlier
- versions) has bugs similar to the one noted above. There are
- both compiler and JVM bugs; the JVM bugs prevent the correct
- byte codes (as produced by the Java 2 SDK) from working. This
- means that you can't compile or use this DOM code with Microsoft
- implementations of Java until Microsoft fixes these bugs, which
- have been reported to Microsoft.
+ <ul>
+ <li>This software is a "Java Optional Package" for XML processing.
+ </li>
+ <li>If you recompile the DOM implementation using versions of "javac"
+ older than the Java 2 SDK version 1.2 you may run into a compiler
+ bug. The symptom is a report of illegal access violations for some
+ of the private classes inside the DOM implementation. This is
+ because of incorrect code generated by the compiler. You should
+ only compile these class files with a compiler that does not have
+ this bug; you may also use the pre-compiled version in this
+ release. There is no bytecode dependency on the Java 2 runtime;
+ you may use these classes on JDK 1.1 systems also.
+ </li>
+ <li>The Microsoft SDK 3.2 for Java (and presumably all earlier
+ versions) has bugs similar to the one noted above. There are both
+ compiler and JVM bugs; the JVM bugs prevent the correct byte codes
+ (as produced by the Java 2 SDK) from working. This means that you
+ can't compile or use this DOM code with Microsoft implementations
+ of Java until Microsoft fixes these bugs, which have been reported
+ to Microsoft.
+ </li>
+ </ul>
-</UL>
+ <hr width="70%">
-<h4> Changes since JAXP RI (Reference Implementation) version 1.0.1 </h4>
+ <h4>Changes since JAXP RI (Reference Implementation) version 1.0.1</h4>
<ul>
<li>All previous releases (from version 1.0.1 and before) used a
parser implementation with a package heirarchy beginning with
@@ -234,18 +176,27 @@
<code>javax.xml.parsers.SAXParser.getParser()</code> method.
</li>
</ul>
-<!--
-<H4> Changes since EA1 </H4>
-<UL>
-
- <LI> API for pluggability has changed. See the specification and
- javadocs for more details.
-
- <LI> All the reported bugs have been fixed including those reported
- internally for SAX 1.0 DOM Level 1 and the JAXP 1.0 API.
+ <h4>Changes since 1.0</h4>
+ <ul>
+ <li>Default parser is used in controlled environments such as applets
+ where <code>System.getProperty()</code> results in a
+ SecurityException.
+ </li>
+ <li>Default Message.properties is provided to avoid gettting error codes
+ in Locales other than English.
+ </li>
+ </ul>
-</UL>
--->
+ <h4>Changes since EA1</h4>
-</BODY></HTML>
+ <ul>
+ <li>API for pluggability has changed. See the specification and
+ javadocs for more details.
+ </li>
+ <li>All the reported bugs have been fixed including those reported
+ internally for SAX 1.0 DOM Level 1 and the JAXP 1.0 API.
+ </li>
+ </ul>
+ </body>
+</html>
1.2 +100 -102 xml-crimson/docs/readme.html
Index: readme.html
===================================================================
RCS file: /home/cvs/xml-crimson/docs/readme.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- readme.html 2000/11/23 01:53:40 1.1
+++ readme.html 2001/01/26 02:14:02 1.2
@@ -1,10 +1,10 @@
-<HTML>
- <HEAD>
- <!-- $Id: readme.html,v 1.1 2000/11/23 01:53:40 edwingo Exp $ -->
- <TITLE>
+<html>
+ <head>
+ <!-- $Id: readme.html,v 1.2 2001/01/26 02:14:02 edwingo Exp $ -->
+ <title>
Java API for XML Processing
- </TITLE>
- <STYLE>
+ </title>
+ <style>
<!--
BODY {
font-family: Lucida, Helvetica, Univers, sans-serif;
@@ -17,19 +17,19 @@
font-family: Courier, monospace;
}
-->
- </STYLE>
- </HEAD>
- <BODY BGCOLOR="#eeeeff">
+ </style>
+ </head>
+ <body bgcolor="#eeeeff">
- <H1>Java API for XML Processing<br>
+ <h1>Java<sup><font size="-2">TM</font></sup> API for XML Processing<br>
README
- </H1>
+ </h1>
<center>
<b>Version:</b> 1.1ea2 (Early Access 2)<br>
</center>
<p>
- The Java API for XML Processing (JAXP) Optional Package enables basic
+ The Java API for XML Processing (JAXP) optional package enables basic
functionality for reading and manipulating XML documents through pure
Java APIs. The API provides a standard way for any XML-conformant
parser and XSLT-conformant processor to be accessed by an
@@ -53,13 +53,18 @@
build fully-functional XML-enabled Java applications for e-commerce,
application integration, and web publishing.</p>
- <p>JAXP 1.1 adds additional functionality over the previous version
- 1.0. In particular, version 1.1 includes an XSLT framework based on
- the TRaX (Transformations for XML) API plus some minor updates to the
- parsing API to support DOM Level 2 and SAX version 2.0.
+ <p>The JAXP 1.1 API adds additional functionality over the previous
+ version 1.0. In particular, version 1.1 includes an XSLT framework
+ based on the TRaX (Transformations for XML) API plus some minor
+ updates to the parsing API to support DOM Level 2 and SAX version
+ 2.0.
</p>
- <h2> Conformance </h4>
+ <p>You may download the current version of this package by following the
+ links from <a
+ href="http://java.sun.com/xml">http://java.sun.com/xml</a>.
+ </p>
+<h2>Conformance </h2>
<p>This release aims to be conformant to the following
specifications:
@@ -68,7 +73,8 @@
<li><a
href="http://java.sun.com/aboutJava/communityprocess/review.html">
JAXP 1.1</a> JSR-63</li>
- <li><a href="http://www.w3.org/TR/2000/REC-xml-20001006">XML 1.0</a></li>
+ <li><a href="http://www.w3.org/TR/2000/REC-xml-20001006">XML 1.0
+ Second Edition</a></li>
<li><a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">
XML Namespaces</a></li>
<li><a href="http://www.megginson.com/SAX/index.html">SAX 2.0</a></li>
@@ -79,99 +85,91 @@
<li><a href="http://www.w3.org/TR/1999/REC-xslt-19991116">
XSLT 1.0</a></li>
</ul>
-<!--
-<P> You may download the current version of this package by following the
-links from
-<a href="http://java.sun.com/xml">
-http://java.sun.com/xml</a>.
--->
-
-<!--
-<UL>
- <LI><a href=#license>Software License</a>
- <LI><a href=#installation>Installation Instructions</a>
- <LI><a href=#documentation>Documentation</a>
- <LI><a href=#feedback>Feedback</a>
-
- </UL>
--->
- <hr width="70%" />
-
- <a name=license>
- <h2> Software License </h2>
- </a>
+
+ <a name="license"></a>
+ <h2> Software Licenses </h2>
<p>The software in the packages <code>javax.xml.parsers</code> and
- <code>javax.xml.transform</code> are covered by the <a
+ <code>javax.xml.transform</code> is covered by the <a
href="License-RI.html">JAXP Reference Implementation Pre-release
License</a>. The software under the package hierarchies beginning
- with <code>org.w3c.dom</code> are covered by the <a
+ with <code>org.w3c.dom</code> is covered by the <a
href="License-W3C.html">W3C Software License</a>. All of the
remaining software in this distribution is covered by the <a
- href=License-ASF>Apache Software License</a>.
+ href="License-ASF">Apache Software License</a>.
+ </p>
+
+ <a name="installation"></a>
+ <h2>Installation Instructions</h2>
+
+ <p>To use this software, you need any version of the Java<sup><font
+ size="-2">TM</font></sup> 2 Software
+ Development Kit (SDK) or version 1.1.8 of the Java Development Kit
+ (JDK) or above. Java development kits for various platforms can be
+ downloaded from several sites such as one provided by Sun
+ Microsystems at <a
+ href="http://java.sun.com/j2se">http://java.sun.com/j2se</a>.
+ </p>
+
+ <p> See the <a href="install.html">Installation instructions</a>
+ for more information.
</p>
-<!--
-Please read the <a href=LICENSE>License Agreement</a>
-that applies to this software.
--->
-
-<a name=installation>
-<H2> Installation Instructions </H2>
-</a>
-
-To use this software, you need any version of the Java 2 Software
-Development Kit (SDK) or version 1.1.8 of the Java Development Kit (JDK) or
-above. Java development kits for various platforms can be downloaded from
-several sites such as one provided by Sun Microsystems at <a
-href="http://java.sun.com/j2se">http://java.sun.com/j2se</a>.
+ <a name="documentation"></a>
+ <h2>Documentation</h2>
+ At this time, the documentation for this release consists of:
+ <ul>
+ <li> <a href="docs/api/index.html">Javadoc API documentation</a> </li>
+ <li> <a href="relnotes.html">Release notes</a></li>
+ <li> <a href="examples/index.html">Example XML documents and programs</a>
+ </li>
+ </ul>
-<!-- You
-need approximately 3.5M of disk space to hold the library and its
-documentation. -->
-
-<P> See the <a href=install.html>Installation Instructions</a>
-for more information.
-
-
-<a name=documentation>
-<H2> Documentation </H2>
-</a> At this time, the documentation for this package is primarily:
-<ul>
- <li> <a href=docs/api/index.html>Javadoc documentation</a> </li>
- <li> <a href=relnotes.html>Release Notes</a></li>
- <li> <a href="examples/index.html">XML and API examples</a> </li>
-</ul>
-
-<P> Developers should note that this API documentation uses
-the Java 2 Software Development Kit (SDK) <em>javadoc</em> features,
-so that the summary pages (listing the packages and the contents
-of each package) are considerably more useful than in older versions.
-Each summary now has an explanation of its significant
-features and (as a rule) how to use the package.
-
-
-<a name=feedback>
- <h2> Feedback and XML Discussion Forums </h2>
-</a>
- <p> Please send feedback on this software to the <a
- href="mailto:xml-feedback@java.sun.com">xml-feedback@java.sun.com</a>
- mailing address. This address is not a mailing list so you cannot
- subscribe. However, there are two mailing lists hosted by Sun for XML
- that you can subscribe to. One of these lists is the <a
- href="mailto:xml-interest@java.sun.com">xml-interest@java.sun.com</a>
- mailing list where general discussions about XML occur. To subscribe
- go to <a href="http://java.sun.com/xml">http://java.sun.com/xml</a> and
- follow the instructions listed there.</p>
-
- <p> For very technical "Developers Only" discussions, you may also be
- interested in the <em>XML-Dev</em> list. An <a
- href=http://lists.xml.org/archives/xml-dev>archive of that mailing
- list</a> is available.</p>
+ <p>Developers should note that this API documentation uses
+ the Java 2 SDK <code>javadoc</code> features, so that the summary
+ pages (listing the packages and the contents of each package) are
+ considerably more useful than in older versions. Each summary now
+ has an explanation of its significant features and (as a rule) how to
+ use the package.
+ </p>
-<p> The newsgroup <a href=news:comp.text.xml>comp.text.xml</a> may also be
-of interest.</p>
+
+ <a name="feedback"></a>
+ <h2>Feedback and XML Discussion Forums</h2>
+ <p>Please send feedback on this software to the <a
+ href="mailto:xml-feedback@java.sun.com">xml-feedback@java.sun.com</a>
+ mailing address. This address is not a subscribe-able mailing list;
+ however, there are two XML related mailing lists hosted by Sun that
+ you can subscribe to:
+ </p>
+ <ul>
+ <li><a href="mailto:xml-interest@java.sun.com">
+ xml-interest@java.sun.com</a>: for general discussions
+ about XML
+ </li>
+ <li>xml-announce@java.sun.com: a low volume mailing
+ list for Sun announcements to the community about XML</li>
+ </ul>
+ <p>To subscribe, go to <a href="http://java.sun.com/xml">
+ http://java.sun.com/xml</a> and follow the directions listed
+ there.</p>
-<P> <hr>
-Java is a trademark of Sun Microsystems, Inc.<br>
+ <p>Other non-Sun discussion forms are:</p>
+ <ul>
+ <li>Apache XML mailing lists: see <a href="http://xml.apache.org/">
+ http://xml.apache.org/</a>
+ </li>
+
+ <li><code>xml-dev</code>: for technical discussions. An <a
+ href="http://lists.xml.org/archives/xml-dev">
+ archive</a> of this mailing list is available.
+ </li>
+
+ <li>The newsgroup <a href="news:comp.text.xml">comp.text.xml</a>
+ may also be of interest.
+ </li>
+ </ul>
-</BODY></HTML>
+ <hr>
+ <p>Java is a trademark of Sun Microsystems, Inc.</p>
+ </body>
+</html>
1.2 +63 -169 xml-crimson/docs/install.html
Index: install.html
===================================================================
RCS file: /home/cvs/xml-crimson/docs/install.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- install.html 2000/11/23 01:53:40 1.1
+++ install.html 2001/01/26 02:14:02 1.2
@@ -1,9 +1,10 @@
-<HTML><HEAD>
- <!-- $Id: install.html,v 1.1 2000/11/23 01:53:40 edwingo Exp $ -->
- <TITLE>
+<html>
+ <head>
+ <!-- $Id: install.html,v 1.2 2001/01/26 02:14:02 edwingo Exp $ -->
+ <title>
Java API for XML Processing -- Installation
- </TITLE>
- <STYLE>
+ </title>
+ <style>
<!--
BODY {
font-family: Lucida, Helvetica, Univers, sans-serif;
@@ -16,172 +17,65 @@
font-family: Courier, monospace;
}
-->
- </STYLE>
-</HEAD><BODY BGCOLOR="#eeeeff">
+ </style>
+ </head>
+ <body bgcolor="#eeeeff">
+
+ <h1>Java<sup><font size="-2">TM</font></sup> API for XML Processing<br>
+ Installation
+ </h1>
+ <center>
+ <b>Version:</b> 1.1ea2 (Early Access 2)<br>
+ </center>
+
+ <h2>System Requirements</h2>
+
+ This version of the Java API for XML Processing requires:
+ <ul>
+ <li>JDK 1.1.8 or later (including any version of Java 2)</li>
+ <li>At least 8MB of free disk space</li>
+ </ul>
+
+ <h2>Installation</h2>
+
+ <ol>
+ <li>Download the zip file.</li>
+ <li>Unzip and install the file.
+ <p>You may use the <code>jar</code> command from the JDK or Java 2
+ SDK to unzip the distribution or use another platform specific
+ utility to do this. Unzipping the file creates a directory of the
+ form <code>jaxp-<version></code> within the extraction directory.
+ </p>
+ </li>
+
+ <li>Update the java classpath.
+ <p>You can either update the <code>CLASSPATH</code> environment
+ variable to include the three jar files, or you can install the
+ jar files as an extension to Java 2.
+ </p>
+
+ <p>To update the <code>CLASSPATH</code> variable, add the following
+ components. Let <code>$XML</code> represent the directory where
+ you installed JAXP.
+ </p>
+ <ul>
+ <li>On Unix:<br />
+ <code>$XML/jaxp.jar:$XML/crimson.jar:$XML/xalan.jar</code></li>
+ <li>On Win32:<br />
+ <code>$XML\jaxp.jar;$XML\crimson.jar;$XML\xalan.jar</code></li>
+ </ul>
+ <p>To install these jar files as an extension of Java 2, copy them to
+ the <code>$JAVA_HOME/jre/lib/ext</code> directory. (The
+ <code>JAVA_HOME</code> directory is the one that contains
+ <code>bin/java</code>.) This eliminates the need to modify class
+ paths. (This technique may also be used with the Java Plug-in.)</p>
+ </li>
+
+ <li>Run the sample programs. Please refer to <a
+ href="examples/index.html">information on examples</a>.
+ </li>
-
-<H1>
-Java API for XML Processing
-<br>
-Installation
-</H1>
-<center>
-<b>Version:</b> 1.1ea (Early Access)<br>
-</center>
-
-<H2> System Requirements </H2>
-
-This version of the Java API for XML Processing requires:
-<UL>
- <li>JDK 1.1.8 or later (including any version of Java 2)</li>
- <li>At least 8MB of free disk space</li>
-</UL>
-
-<!--
-<p>In addition, the PATH and JAVA_HOME environment variables must reference the JDK or Java 2 SDK. If you have not already done this, use the following instructions:
-
-<P>On Solaris, if you've installed the JDK in <em>/java</em>:
-<code>
-<PRE>
- % set PATH=(/java/bin $PATH)
- % setenv JAVA_HOME /java
-</PRE>
-</code>
-
- On Win32 systems, if you have installed the JDK or Java 2 SDK in
- <em>D:\java</em>:<code><PRE>
- C:\> set PATH=D:\java\bin;%PATH%
- C:\> set JAVA_HOME=D:\java
- </PRE></code>
--->
-
-<H2> Installation </H2>
-
-<OL>
-
- <li>Download the ZIP/Install file.</li>
-<!--
-
-<p> Log on to the Java Developer Connection site and select the download
-file for the platform you are using (Windows or Unix).</p>
-
-<p>On Unix, download or copy the file to the location where you want to
-install the software.</p>
-
- <P>
--->
- <li> UnZip/Install the file.</li>
-<!--
-<p>
-<em>On Unix systems</em>, uncompress the downloaded <em>jaxp-1_0_1.zip</em>
-ZIP file.
-
-<p> You may use the JAR command from the JDK or Java 2 SDK to unzip the
- distribution: <blockquote>
- <code>jar xvf jaxp-1_0_1.zip</code></blockquote>
-
-<p>
- Alternatively, you may use an <em>UnZip</em> utility. <a href=http://www.cdrom.com/pub/infozip/>Info-ZIP</a>
- is one such utility, available on a variety of
- operating systems.
-
-<p>Unzipping the file creates a directory called jaxp1.0.1 within the current directory.
-
-<p>
-<em>On Windows systems</em>, simply run the downloaded <em>jaxp-1_0_1-win.exe</em>
-file.
-By default, this program uses the following directory: <br>
-c:\Program Files\javasoft\jaxp1.0.1
-<p> You may change the destination directory at setup time.
- <P>
--->
-<!--
- <LI> <em>Check the contents of the distribution.</em>
-
-<p>
-After the software is unzipped or installed, the new directory should contain the following files:
-
- <P><CENTER><TABLE BORDER=1 BGCOLOR="#ffffcc">
-
- <TR><TD><b>LICENSE</b></TD>
- <TD> The license applying to this software </TD></TR>
-
- <TR><TD><b>docs/api/* </b></TD>
- <TD> Javadoc generated files presenting library APIs </TD></TR>
-
- <TR><TD><b>examples/* </b></TD>
- <TD> Example files, in subdirectories </TD></TR>
-
- <TR><TD><b>examples/index.html </b></TD>
- <TD> Index to the example files </TD></TR>
-
- <TR><TD><b>readme.html</b></TD>
- <TD> README for this release </TD></TR>
-
- <TR><TD><b>install.html</b></TD>
- <TD> This file </TD></TR>
-
- <TR><TD><b>relnotes.html</b></TD>
- <TD> Release notes </TD></TR>
-
- <TR><TD><b>jaxp.jar</b></TD>
- <TD> Java Archive file containing the javax classes </TD></TR>
-
- <TR><TD><b>parser.jar</b></TD>
- <TD> Java Archive file containing the implementation classes </TD></TR>
-
- </TABLE></CENTER>
-
- <P>
-
--->
- <li>Update the CLASSPATH.</li>
-
-<P> You can either update the CLASSPATH variable to include the three jar
-files, or you can install the JAR files as an extension to Java 2.</p>
-
-<p>To update the CLASSPATH variable, add the following entry to the
-variable (where <code>$XML</code> is the base directory in which the XML
-library is installed):</p>
-<p>
-<ul>
- <li> Unix:
- <code>$XML/jaxp.jar:$XML/crimson.jar:$XML/xalan.jar
- </code></li>
- <li> Win32:
- <code>$XML\jaxp.jar;$XML\crimson.jar;$XML\xalan.jar
- </code></li>
-</ul>
-</p>
- <p> To install these JAR files as an extension of Java 2, copy them to
- the <code>$JAVA_HOME/jre/lib/ext</code> directory. (The
- <code>JAVA_HOME</code> directory is the one that contains
- <code>bin/java</code>.) This eliminates the need to modify class
- paths. (This technique may also be used with the Java Plug-in.)</p>
-
-<!--
- <LI> <em>Run the sample programs.</em>
-
-<p>
- To run the sample programs, first compile them, then
- run them following the invocation instructions in the Makefile (for Solaris) or batch file (for Win32).
-
-<P>The Makefiles and batch files should work with minimal changes, if any. The files will build the classes as necessary, assuming that the JDK is set up correctly.
-For example:<PRE>
- % cd $XML/examples/simple
- % make
- <em>... output</em>
- %
- </PRE>
- <br>
- or in Windows: <PRE>
- C:\Program Files\javasoft\jaxp1.0.1> cd examples\simple
- C:\Program Files\javasoft\jaxp1.0.1\examples\simple> build
- <em>... output</em>
- C:\Program Files\javasoft\jaxp1.0.1\examples\simple>
- </PRE>
--->
-</OL>
+</ol>
<!--
<p> Note that due to code generation problems in the 1.1 "javac" and