db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kahat...@apache.org
Subject svn commit: r1078819 - /db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita
Date Mon, 07 Mar 2011 15:50:52 GMT
Author: kahatlen
Date: Mon Mar  7 15:50:52 2011
New Revision: 1078819

URL: http://svn.apache.org/viewvc?rev=1078819&view=rev
Log:
DERBY-5095: Update XML operator documentation to reflect new requirements

Modified:
    db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita

Modified: db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita?rev=1078819&r1=1078818&r2=1078819&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita Mon Mar  7 15:50:52 2011
@@ -67,31 +67,33 @@ into an XML document.</note>
 are described in the section on expressions on LONG data types in 
 <xref href="cdevstandards806118.dita#cdevstandards806118"></xref>.</p>
 <p>For the XML operators to work properly, <ph conref="../conrefs.dita#prod/productshortname"></ph>
requires
-that a JAXP parser, such as Apache Xerces, and Apache Xalan are included in
-the Java classpath. If either the parser or Xalan are missing from the classpath, 
+that a JAXP parser, such as Apache Xerces, and an implementation of
+the DOM Level 3 XPath specification, such as Apache Xalan, are
+included in the Java classpath. If either the parser or the XPath
+processor is missing from the classpath,
 <ph conref="../conrefs.dita#prod/productshortname"></ph> disallows any XML-related
 operations.  </p>
 <section><title>Classpath and version issues</title>
-<p>Most Java Virtual Machines (JVMs) that are version 1.4 or later have
-a JAXP parser embedded in the JVM. If you are using one of these JVMs, you
-may not need to add any classes to your classpath. Some exceptions exist:</p>
-<ul>
-<li>In most version 1.4.2 JVMs, the version of Xalan that comes with the JVM is 
-not new enough, so you must override the version of Xalan in the JVM with a
+<p>Most Java Virtual Machines (JVMs) that are version 1.6 or later,
+have the required libraries embedded in the JVM. If you are using one
+of these JVMs, you may not need to add any classes to your classpath.
+</p>
+<p>
+If your JVM does not include the required libraries, you must add
+Apache Xalan, or some other library that implements the required
+functionality, to your classpath.
+</p>
+<p>
+Some JVMs include a version of Xalan that is not new enough. If your
+JVM comes with a too old version of Xalan, you may need to override
+the version of Xalan in the JVM with a
 newer version by using the Endorsed Standards Override Mechanism described at
 <xref format="html" href="http://download.oracle.com/javase/1.4.2/docs/guide/standards/"
 scope="external">http://download.oracle.com/javase/1.4.2/docs/guide/standards/</xref>.
To
 use this mechanism, download and install a binary distribution of Xalan from
 Apache and set the system property <codeph>java.endorsed.dirs</codeph> to point
-to the Xalan installation directory.</li>
-<li>After JVM version 1.4, Sun renamed the JAXP packages. 
-<ph conref="../conrefs.dita#prod/productshortname"></ph> cannot find these
-renamed packages. If you are using a Sun JVM later than version 1.4, download
-and install a binary
-distribution of Xalan from Apache and place the <codeph>xalan.jar</codeph> file
-in your classpath. The <codeph>xalan.jar</codeph> file automatically puts into
-the classpath the other required jars that are in the same directory.</li>
-</ul>
+to the Xalan installation directory.
+</p>
 </section>
 </conbody>
 </concept>



Mime
View raw message