You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by mr...@apache.org on 2005/07/20 06:16:48 UTC
cvs commit: xml-xerces/java/docs install.xml
mrglavas 2005/07/19 21:16:48
Modified: java/docs install.xml
Log:
Note that Xerces-J also supports javax.xml.datatype and javax.xml.validation.
Revision Changes Path
1.23 +9 -8 xml-xerces/java/docs/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/install.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- install.xml 9 May 2005 03:36:24 -0000 1.22
+++ install.xml 20 Jul 2005 04:16:47 -0000 1.23
@@ -71,14 +71,15 @@
<tr>
<td>xercesImpl.jar</td>
<td>Jar file containing all the parser class files that implement
- one of the standard API's supported by the parser</td>
+ one of the standard APIs supported by the parser</td>
</tr>
<tr>
<td>xml-apis.jar</td>
- <td>Jar file containing all the standard API's implemented by
+ <td>Jar file containing all the standard APIs implemented by
the parser. Currently, &ParserName; supports DOM level 3, SAX
- 2.0.2, and the <code>javax.xml.parsers</code> part of JAXP
- 1.3. </td>
+ 2.0.2, and the <code>javax.xml.datatype</code>,
+ <code>javax.xml.parsers</code> and <code>javax.xml.validation</code>
+ parts of JAXP 1.3.</td>
</tr>
<tr>
<td>xercesSamples.jar</td>
@@ -207,14 +208,14 @@
<s2 title='Changes in Xerces jar files'>
<p>In order to accomodate the very common case in which Xerces is
used with an XSLT processor such as Xalan, between Xerces 2.0.0 beta 3
- and beta 4 a change in the default organization of Xerces's jar
+ and beta 4 a change in the default organization of Xerces' jar
files was introduced. As well as the <code>xercesSamples.jar</code>
file, which we still produce, Xerces formerly came with a file called
<code>xerces.jar</code>. This file contained all of the
parser's functionality. Two files are now included:
- <code>xercesImpl.jar</code>, our implementation of various API's,
- and <code>xml-apis.jar</code>, the API's themselves. This
- was done so that, if your XSLT processor ships with API's at the
+ <code>xercesImpl.jar</code>, our implementation of various APIs,
+ and <code>xml-apis.jar</code>, the APIs themselves. This
+ was done so that, if your XSLT processor ships with APIs at the
same level as those supported by &ParserName;, you can avoid putting
<code>xml-apis.jar</code> on your classpath.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xerces.apache.org
For additional commands, e-mail: commits-help@xerces.apache.org