You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by ch...@apache.org on 2014/06/24 16:32:04 UTC
svn commit: r1605094 - in /db/derby/docs/trunk/src:
devguide/cdevstandardsxml.dita ref/rreffuncxmlexists.dita
ref/rreffuncxmlparse.dita ref/rreffuncxmlquery.dita
ref/rreffuncxmlserialize.dita ref/rreflimitsxml.dita ref/rrefsqljtypexml.dita
Author: chaase3
Date: Tue Jun 24 14:32:04 2014
New Revision: 1605094
URL: http://svn.apache.org/r1605094
Log:
DERBY-6633 Remove DOM level 3 XPath requirement from description of XML operators
Modified 6 Reference Manual and 1 Developer's Guide topics.
Patch: DERBY-6633-2.diff
Modified:
db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita
db/derby/docs/trunk/src/ref/rreffuncxmlexists.dita
db/derby/docs/trunk/src/ref/rreffuncxmlparse.dita
db/derby/docs/trunk/src/ref/rreffuncxmlquery.dita
db/derby/docs/trunk/src/ref/rreffuncxmlserialize.dita
db/derby/docs/trunk/src/ref/rreflimitsxml.dita
db/derby/docs/trunk/src/ref/rrefsqljtypexml.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=1605094&r1=1605093&r2=1605094&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita Tue Jun 24 14:32:04 2014
@@ -66,34 +66,11 @@ into an XML document.</note>
<p>The XML data type is not allowed in any of the clauses or operations that
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 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 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://docs.oracle.com/javase/1.5.0/docs/guide/standards/"
-scope="external">http://docs.oracle.com/javase/1.5.0/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.
-</p>
-</section>
+<p>For the XML operators to work properly,
+<ph conref="../conrefs.dita#prod/productshortname"></ph> requires that the
+Java Virtual Machine (JVM) have working implementations of the
+<i>javax.xml.parsers.DocumentBuilderFactory</i> and
+<i>javax.xml.xpath.XPathFactory</i> classes. All supported JVMs implement these
+classes.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/ref/rreffuncxmlexists.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rreffuncxmlexists.dita?rev=1605094&r1=1605093&r2=1605094&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rreffuncxmlexists.dita (original)
+++ db/derby/docs/trunk/src/ref/rreffuncxmlexists.dita Tue Jun 24 14:32:04 2014
@@ -28,7 +28,10 @@ values in SQL.</shortdesc>
</metadata></prolog>
<refbody>
<section> <p>The XMLEXISTS operator has two arguments, an XML query expression
-and a <ph conref="../conrefs.dita#prod/productshortname"></ph> XML value.</p> </section>
+and a <ph conref="../conrefs.dita#prod/productshortname"></ph> XML value.</p>
+<p>See "XML data types and operators" in the
+<ph conref="../conrefs.dita#pub/citdevelop"></ph> for more information.</p>
+</section>
<refsyn><title>Syntax</title>
<codeblock><b>XMLEXISTS ( <varname>xqueryStringLiteral</varname>
PASSING BY REF <varname>xmlValueExpression</varname> [ BY REF ] )
@@ -36,16 +39,15 @@ and a <ph conref="../conrefs.dita#prod/p
<dt><varname>xqueryStringLiteral</varname></dt>
<dd>Must be specified as a string literal. If this argument is specified as
a parameter, an expression that is not a literal, or a literal that is not
-a string (for example an integer), <ph conref="../conrefs.dita#prod/productshortname"></ph> throws
-an error. The <varname>xqueryStringLiteral</varname> argument must also be
-an XPath expression that is supported by Apache Xalan. <ph conref="../conrefs.dita#prod/productshortname"></ph> uses
-Apache Xalan to evaluate all XML query expressions. Because Xalan does not
-support full XQuery, neither does <ph conref="../conrefs.dita#prod/productshortname"></ph>.
- If Xalan is unable to compile or execute the query argument, <ph conref="../conrefs.dita#prod/productshortname"></ph> catches
-the error that is thrown by Xalan and throws the error as a SQLException.
-For more on XPath and XQuery expressions, see these Web sites: <xref format="html"
-href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</xref> and <xref
-format="html" href="http://www.w3.org/TR/xquery/">http://www.w3.org/TR/xquery/</xref>.</dd>
+a string (for example an integer),
+<ph conref="../conrefs.dita#prod/productshortname"></ph> throws an error. The
+<varname>xqueryStringLiteral</varname> argument must also be an XPath
+expression. <ph conref="../conrefs.dita#prod/productshortname"></ph> does not
+support full XQuery, only the XPath subset. If it cannot compile or execute the
+query argument, <ph conref="../conrefs.dita#prod/productshortname"></ph> throws
+an <i>SQLException</i>. See <xref format="html"
+href="http://www.w3.org/TR/xpath" scope="external"/> for more information on
+XPath expressions.</dd>
</dlentry><dlentry>
<dt><varname>xmlValueExpression</varname></dt>
<dd>Must be an XML data value and must constitute a well-formed SQL/XML document.
@@ -103,12 +105,5 @@ To create the table, use this statement:
<codeblock><b>CREATE TABLE x_table ( id INT, xcol XML
CHECK (XMLEXISTS ('//student[@age < 25]' PASSING BY REF xcol)) )</b></codeblock></p>
</section>
-<section><title>Usage note</title><p><ph conref="../conrefs.dita#prod/productshortname"></ph> requires
-that a JAXP parser (such as Apache Xerces) and Apache Xalan are listed
-in the Java classpath for the XML functions to work. If either the JAXP parser
-or Xalan is missing from the classpath, attempts to use the XMLEXISTS operator
-will result in an error. In some situations, you may need to take steps to place
-the parser and Xalan in your classpath. See "XML data types and operators" in
-the <ph conref="../conrefs.dita#pub/citdevelop"></ph> for details.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rreffuncxmlparse.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rreffuncxmlparse.dita?rev=1605094&r1=1605093&r2=1605094&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rreffuncxmlparse.dita (original)
+++ db/derby/docs/trunk/src/ref/rreffuncxmlparse.dita Tue Jun 24 14:32:04 2014
@@ -33,20 +33,24 @@ store the result permanently in <ph conr
columns. Whether temporary or permanent, you can use the XML value as an
input to the other <ph conref="../conrefs.dita#prod/productshortname"></ph> XML
operators, such as <xref href="rreffuncxmlexists.dita#rreffuncxmlexists">XMLEXISTS</xref> and <xref
-href="rreffuncxmlquery.dita#rreffuncxmlquery">XMLQUERY</xref>.</p> </section>
+href="rreffuncxmlquery.dita#rreffuncxmlquery">XMLQUERY</xref>.</p>
+<p>See "XML data types and operators" in the
+<ph conref="../conrefs.dita#pub/citdevelop"></ph> for more information.</p>
+</section>
<refsyn><title>Syntax</title>
<codeblock><b>XMLPARSE ( DOCUMENT <varname>stringValueExpression</varname> PRESERVE WHITESPACE )</b></codeblock><dl>
<dlentry>
<dt>DOCUMENT </dt>
-<dd>Required keyword that describes the type of XML input that <ph conref="../conrefs.dita#prod/productshortname"></ph> can
-parse. <ph conref="../conrefs.dita#prod/productshortname"></ph> can only
-parse string expressions that constitute well-formed XML documents. This
-is because <ph conref="../conrefs.dita#prod/productshortname"></ph> uses a
-JAXP parser to parse all string values. The JAXP parser expects the
-<varname>stringValueExpression</varname>
-to constitute a well-formed XML document. If the string does not constitute
-a well-formed document, JAXP throws an error. <ph conref="../conrefs.dita#prod/productshortname"></ph> catches
-the error and throws the error as a SQLException.</dd>
+<dd>Required keyword that describes the type of XML input that
+<ph conref="../conrefs.dita#prod/productshortname"></ph> can parse.
+<ph conref="../conrefs.dita#prod/productshortname"></ph> can only parse string
+expressions that constitute well-formed XML documents, because
+<ph conref="../conrefs.dita#prod/productshortname"></ph> uses a parser from the
+<i>javax.xml.parsers</i> package to parse all string values. The parser expects
+the <varname>stringValueExpression</varname> to constitute a well-formed XML
+document. If the string does not constitute a well-formed document, the parser
+throws an error. <ph conref="../conrefs.dita#prod/productshortname"></ph>
+catches the error and throws the error as an <i>SQLException</i>.</dd>
</dlentry><dlentry>
<dt><varname>stringValueExpression</varname></dt>
<dd>Any expression that evaluates to a SQL character type, such as CHAR, VARCHAR,
@@ -88,13 +92,7 @@ statement:
PRESERVE WHITESPACE)
)</b></codeblock>
You should bind into the statement using the <i>setCharacterStream()</i>
-method, or any other JDBC <i>setXXX</i> method that works for the CAST target type.</p></section>
-<section><title>Usage note</title><p><ph conref="../conrefs.dita#prod/productshortname"></ph> requires
-that a JAXP parser (such as Apache Xerces) and Apache Xalan are listed
-in the Java classpath for the XML functions to work. If either the JAXP parser
-or Xalan is missing from the classpath, attempts to use the XMLPARSE operator
-will result in an error. In some situations, you may need to take steps to place
-the parser and Xalan in your classpath. See "XML data types and operators" in
-the <ph conref="../conrefs.dita#pub/citdevelop"></ph> for details.</p></section>
+method, or any other JDBC <i>setXXX</i> method that works for the CAST target
+type.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rreffuncxmlquery.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rreffuncxmlquery.dita?rev=1605094&r1=1605093&r2=1605094&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rreffuncxmlquery.dita (original)
+++ db/derby/docs/trunk/src/ref/rreffuncxmlquery.dita Tue Jun 24 14:32:04 2014
@@ -28,7 +28,10 @@ in SQL.</shortdesc>
</metadata></prolog>
<refbody>
<section> <p>The XMLQUERY operator has two arguments, an XML query expression
-and a <ph conref="../conrefs.dita#prod/productshortname"></ph> XML value.</p></section>
+and a <ph conref="../conrefs.dita#prod/productshortname"></ph> XML value.</p>
+<p>See "XML data types and operators" in the
+<ph conref="../conrefs.dita#pub/citdevelop"></ph> for more information.</p>
+</section>
<refsyn><title>Syntax</title>
<codeblock><b>XMLQUERY ( <varname>xqueryStringLiteral</varname>
PASSING BY REF <varname>xmlValueExpression</varname>
@@ -39,16 +42,14 @@ and a <ph conref="../conrefs.dita#prod/p
<dd>Must be specified as a string literal. If this argument is specified as
a parameter, an expression that is not a literal, or a literal that is not
a string (for example an integer),
-<ph conref="../conrefs.dita#prod/productshortname"></ph> throws
-an error. The <varname>xqueryStringLiteral</varname> argument must also be
-an XPath expression that is supported by Apache Xalan. <ph conref="../conrefs.dita#prod/productshortname"></ph> uses
-Apache Xalan to evaluate all XML query expressions. Because Xalan does not
-support full XQuery, neither does <ph conref="../conrefs.dita#prod/productshortname"></ph>.
-If Xalan is unable to compile or execute the query argument, <ph conref="../conrefs.dita#prod/productshortname"></ph> catches
-the error that is thrown by Xalan and throws the error as a SQLException.
-For more on XPath and XQuery expressions, see these Web sites: <xref format="html"
-href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</xref> and <xref
-format="html" href="http://www.w3.org/TR/xquery/">http://www.w3.org/TR/xquery/</xref>.</dd>
+<ph conref="../conrefs.dita#prod/productshortname"></ph> throws an error. The
+<varname>xqueryStringLiteral</varname> argument must also be an XPath
+expression. <ph conref="../conrefs.dita#prod/productshortname"></ph> does not
+support full XQuery, only the XPath subset. If it cannot compile or execute the
+query argument, <ph conref="../conrefs.dita#prod/productshortname"></ph> throws
+an <i>SQLException</i>. See <xref format="html"
+href="http://www.w3.org/TR/xpath" scope="external"/> for more information on
+XPath expressions.</dd>
</dlentry><dlentry>
<dt><varname>xmlValueExpression</varname></dt>
<dd>Must be an XML data value and must constitute a well-formed SQL/XML document.
@@ -112,12 +113,5 @@ WHERE
XMLEXISTS('//student[text() = "BC"]' PASSING BY REF xcol)</b></codeblock>
The result set for this query contains a row for only the rows
in <codeph>x_table</codeph> that have a student whose name is BC.</p></section>
-<section><title>Usage note</title><p><ph conref="../conrefs.dita#prod/productshortname"></ph> requires
-that a JAXP parser (such as Apache Xerces) and Apache Xalan are listed
-in the Java classpath for the XML functions to work. If either the JAXP parser
-or Xalan is missing from the classpath, attempts to use the XMLQUERY operator
-will result in an error. In some situations, you may need to take steps to place
-the parser and Xalan in your classpath. See "XML data types and operators" in
-the <ph conref="../conrefs.dita#pub/citdevelop"></ph> for details.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rreffuncxmlserialize.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rreffuncxmlserialize.dita?rev=1605094&r1=1605093&r2=1605094&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rreffuncxmlserialize.dita (original)
+++ db/derby/docs/trunk/src/ref/rreffuncxmlserialize.dita Tue Jun 24 14:32:04 2014
@@ -46,12 +46,15 @@ those transformations are defined in the
the result of XMLSERIALIZE might actually be the same as the original textual
representation, but that is not guaranteed. </p><p>When an XMLSERIALIZE operator
is specified as part of the top-level result set for a query, the result can
-be accessed from JDBC by using whatever JDBC getXXX methods are allowed on
+be accessed from JDBC by using whatever JDBC <i>getXXX</i> methods are allowed on
the <varname>stringDataType</varname> argument that is included in the XMLSERIALIZE
syntax. If you attempt to select the contents of an XML value from a top-level
result set without using the XMLSERIALIZE operator, <ph conref="../conrefs.dita#prod/productshortname"></ph> throws
an error. <ph conref="../conrefs.dita#prod/productshortname"></ph> does not
-implicitly serialize XML values.</p></note></section>
+implicitly serialize XML values.</p></note>
+<p>See "XML data types and operators" in the
+<ph conref="../conrefs.dita#pub/citdevelop"></ph> for more information.</p>
+</section>
<refsyn><title>Syntax</title>
<codeblock><b>XMLSERIALIZE ( <varname>xmlValueExpression</varname> AS <varname>stringDataType</varname> )</b></codeblock>
<dl><dlentry>
@@ -80,12 +83,5 @@ display the results of an XMLQUERY opera
PASSING BY REF xcol EMPTY ON EMPTY)
AS VARCHAR(50))
FROM x_table</b></codeblock></p></section>
-<section><title>Usage note</title><p><ph conref="../conrefs.dita#prod/productshortname"></ph> requires
-that a JAXP parser (such as Apache Xerces) and Apache Xalan are listed
-in the Java classpath for the XML functions to work. If either the JAXP parser
-or Xalan is missing from the classpath, attempts to use the XMLSERIALIZE operator
-will result in an error. In some situations, you may need to take steps to place
-the parser and Xalan in your classpath. See "XML data types and operators" in
-the <ph conref="../conrefs.dita#pub/citdevelop"></ph> for details.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rreflimitsxml.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rreflimitsxml.dita?rev=1605094&r1=1605093&r2=1605094&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rreflimitsxml.dita (original)
+++ db/derby/docs/trunk/src/ref/rreflimitsxml.dita Tue Jun 24 14:32:04 2014
@@ -20,8 +20,8 @@ limitations under the License.
-->
<reference id="rreflimitsxml" xml:lang="en-us">
<title>XML limitations</title>
-<shortdesc>The following table lists limitations on XML data types in <ph
-conref="../conrefs.dita#prod/productshortname"></ph>.</shortdesc>
+<shortdesc>The following table shows the limitation on XML data types in
+<ph conref="../conrefs.dita#prod/productshortname"></ph>.</shortdesc>
<prolog><metadata>
<keywords><indexterm>limitations<indexterm>XML data type</indexterm></indexterm>
<indexterm>XML data type<indexterm>limitations</indexterm></indexterm>
@@ -31,7 +31,7 @@ conref="../conrefs.dita#prod/productshor
<section>
<table frame="all">
<title>XML limitations</title>
-<desc>This table lists the limitations on <ph conref="../conrefs.dita#prod/productshortname"></ph> XML data types.</desc>
+<desc>This table shows the limitation on <ph conref="../conrefs.dita#prod/productshortname"></ph> XML data types.</desc>
<tgroup cols="2" colsep="1" rowsep="1">
<colspec colname="colspec0" colnum="1" colwidth="50*"/>
<colspec colname="colspec1" colnum="2" colwidth="50*"/>
@@ -46,15 +46,6 @@ conref="../conrefs.dita#prod/productshor
<entry colname="colspec0">Length of XML</entry>
<entry colname="colspec1">2,147,483,647 characters</entry>
</row>
-<row>
-<entry colname="colspec0">Use of XML operators</entry>
-<entry colname="colspec1">Requires that the JAXP parser classes (such as Apache
-Xerces) and the Apache Xalan classes are in the classpath. Attempts to use
-XML operators without these classes in the classpath result in an error. In
-some situations, you may need to take steps to place the parser and Xalan in
-your classpath. See "XML data types and operators" in the
-<ph conref="../conrefs.dita#pub/citdevelop"></ph> for details.</entry>
-</row>
</tbody>
</tgroup>
</table>
Modified: db/derby/docs/trunk/src/ref/rrefsqljtypexml.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqljtypexml.dita?rev=1605094&r1=1605093&r2=1605094&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqljtypexml.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsqljtypexml.dita Tue Jun 24 14:32:04 2014
@@ -30,38 +30,44 @@ documents.</shortdesc>
<p>The XML data type is used: <ul>
<li>To store XML documents that conform to the SQL/XML definition of a well-formed
XML(DOCUMENT(ANY)) value.</li>
-<li>Transiently for XML(SEQUENCE) values, that might not be well-formed XML(DOCUMENT(ANY))
-values.</li>
-</ul></p><note>For an application to retrieve, update, query, or otherwise
-access an XML data value, the application must have classes for a JAXP parser
-and for Xalan in the classpath. <ph conref="../conrefs.dita#prod/productshortname"></ph> issues
-an error if either the parser or Xalan is not found. In some situations, you may
-need to take steps to place the parser and Xalan in your classpath. See
-"XML data types and operators" in the
-<ph conref="../conrefs.dita#pub/citdevelop"></ph> for details.</note>
+<li>Transiently, for XML(SEQUENCE) values that might not be well-formed
+XML(DOCUMENT(ANY)) values.</li>
+</ul></p>
<p>Because none of the
JDBC-side support for SQL/XML is implemented in <ph conref="../conrefs.dita#prod/productshortname"></ph>,
it is not possible to bind directly into an XML value or to retrieve an XML
value directly from a result set using JDBC. Instead, you must bind and retrieve
the XML data as Java strings or character streams by explicitly specifying
-the appropriate XML operators, XMLPARSE and XMLSERIALIZE, as part of your
-SQL queries.</p></section>
+the appropriate XML operators,
+<xref href="rreffuncxmlparse.dita">XMLPARSE</xref> and
+<xref href="rreffuncxmlserialize.dita">XMLSERIALIZE</xref>, as part of your SQL
+queries.</p>
+</section>
<refsyn><title>Syntax</title><codeblock><b>XML</b></codeblock> </refsyn>
-<section><title>Corresponding compile-time Java type</title><p>None</p><p>The
-Java type for XML values is java.sql.SQLXML. However, the java.sql.SQLXML
-type is not supported by <ph conref="../conrefs.dita#prod/productshortname"></ph>. </p> </section>
-<section><title>JDBC metadata type (java.sql.Types)</title><p>None</p><p>The
+<section><title>Corresponding compile-time Java type</title><p>None.</p><p>The
+Java type for XML values is <i>java.sql.SQLXML</i>. However, the
+<i>java.sql.SQLXML</i> type is not supported by
+<ph conref="../conrefs.dita#prod/productshortname"></ph>.</p>
+</section>
+<section><title>JDBC metadata type (java.sql.Types)</title><p>None.</p><p>The
metadata type for XML values is SQLXML. However, the SQLXML type is not supported
by <ph conref="../conrefs.dita#prod/productshortname"></ph>. </p><p>To retrieve
XML values from a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
-using JDBC, use the XMLSERIALIZE operator in the SQL query. For example:<codeblock>SELECT XMLSERIALIZE (xcol as CLOB) FROM myXmlTable </codeblock
->Then retrieve the XML value by using the getXXX method that corresponds to
-the target serialization type, in this example CLOB data types.</p><p>To store
+using JDBC, use the XMLSERIALIZE operator in the SQL query. For example:
+<codeblock>SELECT XMLSERIALIZE (xcol as CLOB) FROM myXmlTable </codeblock>
+Then retrieve the XML value by using the <i>getXXX</i> method that corresponds
+to the target serialization type, in this example CLOB data types.</p><p>To store
an XML value into a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
-using JDBC, use the XMLPARSE operator in the SQL statement. For example: <codeblock>INSERT INTO myXmlTable(xcol) VALUES XMLPARSE(
+using JDBC, use the XMLPARSE operator in the SQL statement. For example:
+<codeblock>INSERT INTO myXmlTable(xcol) VALUES XMLPARSE(
DOCUMENT CAST (? AS CLOB) PRESERVE WHITESPACE)
-</codeblock>Then use any of the setXXX methods that are compatible with String
-types, in this example use the PreparedStatement.setString or PreparedStatement.setCharacterStream
-method calls to bind the operator.</p> </section>
+</codeblock>
+Then use any of the <i>setXXX</i> methods that are compatible with <i>String</i>
+types. In this example, use the <i>PreparedStatement.setString</i> or
+<i>PreparedStatement.setCharacterStream</i> method calls to bind the
+operator.</p>
+<p>See "XML data types and operators" in the
+<ph conref="../conrefs.dita#pub/citdevelop"></ph> for more information.</p>
+</section>
</refbody>
</reference>