db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1567962 - /db/derby/docs/trunk/src/ref/
Date Thu, 13 Feb 2014 15:56:39 GMT
Author: chaase3
Date: Thu Feb 13 15:56:38 2014
New Revision: 1567962

URL: http://svn.apache.org/r1567962
Log:
DERBY-6236  Remove references to old JVMs (pre-Java 6) from the user guides

Modified 10 Reference Manual topics and removed 8.

Patch: DERBY-6236-ref.diff

Removed:
    db/derby/docs/trunk/src/ref/rrefjdbc4_0connection.dita
    db/derby/docs/trunk/src/ref/rrefjdbc4_0dataSource.dita
    db/derby/docs/trunk/src/ref/rrefjdbc4_0databaseMetaData.dita
    db/derby/docs/trunk/src/ref/rrefjdbc4_0sqlexception.dita
    db/derby/docs/trunk/src/ref/rrefjdbc4_0statement.dita
    db/derby/docs/trunk/src/ref/rrefjdbc4_0summary.dita
    db/derby/docs/trunk/src/ref/rrefjdbc4_1datasource.dita
    db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita
Modified:
    db/derby/docs/trunk/src/ref/crefjdbc12657.dita
    db/derby/docs/trunk/src/ref/refderby.ditamap
    db/derby/docs/trunk/src/ref/rrefapi1003363.dita
    db/derby/docs/trunk/src/ref/rrefjdbc15905.dita
    db/derby/docs/trunk/src/ref/rrefjdbc16643.dita
    db/derby/docs/trunk/src/ref/rrefjdbc32052.dita
    db/derby/docs/trunk/src/ref/rrefjdbc4_1summary.dita
    db/derby/docs/trunk/src/ref/rrefjdbc4_2summary.dita
    db/derby/docs/trunk/src/ref/rrefjdbcrefsqlxml.dita
    db/derby/docs/trunk/src/ref/rrefjta18596.dita

Modified: db/derby/docs/trunk/src/ref/crefjdbc12657.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/crefjdbc12657.dita?rev=1567962&r1=1567961&r2=1567962&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/crefjdbc12657.dita (original)
+++ db/derby/docs/trunk/src/ref/crefjdbc12657.dita Thu Feb 13 15:56:38 2014
@@ -33,9 +33,9 @@ of the types described under "JDBC Archi
 href="http://www.oracle.com/technetwork/java/overview-141217.html"
 scope="external">http://www.oracle.com/technetwork/java/overview-141217.html</xref>).
 </p>
-<p>This section provides reference information about <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
-implementation of the JDBC API and documents the way it conforms to the JDBC
-3.0 and 4.0 APIs.</p>
+<p>This section provides reference information about
+<ph conref="../conrefs.dita#prod/productshortname"></ph>'s implementation of
the
+JDBC API and documents the way it conforms to the JDBC APIs.</p>
 <p>See the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>
for
 task-oriented instructions on working with the driver.</p>
 <p>This JDBC driver implements the standard JDBC interfaces.
@@ -47,7 +47,10 @@ In client/server mode, the client applic
 the JDBC server over a network; the server, in turn, which runs in the same
 JVM as <ph conref="../conrefs.dita#prod/productshortname"></ph>, sends requests
 to <ph conref="../conrefs.dita#prod/productshortname"></ph> through the embedded
-JDBC driver. </p>
+JDBC driver.</p>
+<p>For information on the DataSource implementations provided by
+<ph conref="../conrefs.dita#prod/productshortname"></ph>, see
+<xref href="rrefapi1003363.dita#rrefapi1003363"></xref>.</p>
 <p><indexterm>SQLState XJZZZ<indexterm>meaning of</indexterm></indexterm>The
<ph
 conref="../conrefs.dita#prod/productshortname"></ph> JDBC implementation provides
 access to <ph conref="../conrefs.dita#prod/productshortname"></ph> databases

Modified: db/derby/docs/trunk/src/ref/refderby.ditamap
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/refderby.ditamap?rev=1567962&r1=1567961&r2=1567962&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/refderby.ditamap (original)
+++ db/derby/docs/trunk/src/ref/refderby.ditamap Thu Feb 13 15:56:38 2014
@@ -1083,6 +1083,8 @@ URL syntax"></topicref>
 </topicref>
 <topicref href="rrefjdbc30469.dita" navtitle="java.sql.SQLWarning class">
 </topicref>
+<topicref href="rrefjdbcrefsqlxml.dita" navtitle="java.sql.SQLXML interface">
+</topicref>
 <topicref href="rrefjdbcjavasqlsavepoint.dita" navtitle="java.sql.Savepoint interface">
 </topicref>
 <topicref href="rrefjdbc20377.dita" navtitle="Mapping of java.sql.Types to SQL types">
@@ -1091,27 +1093,9 @@ URL syntax"></topicref>
 </topicref>
 </topicref>
 </topicref>
-<topicref href="rrefjdbcjsr169.dita" navtitle="JDBC Package for Connected Device Configuration/Foundation
Profile
-(JSR169)"></topicref>
-<topicref collection-type="family" href="rrefjdbc4_0summary.dita" navtitle="Features supported
on all JDBC 4 releases">
-<topicref href="rrefjdbc4_0sqlexception.dita" navtitle="Refined subclasses of SQLException">
-</topicref>
-<topicref href="rrefjdbc4_0connection.dita" navtitle="java.sql.Connection interface: JDBC
4.0 features">
-</topicref>
-<topicref href="rrefjdbc4_0databaseMetaData.dita" navtitle="java.sql.DatabaseMetaData
interface: JDBC 4.0 features">
-</topicref>
-<topicref href="rrefjdbc4_0statement.dita" navtitle="java.sql.Statement interface: JDBC
4.0 features">
-</topicref>
-<topicref href="rrefjdbc4_0dataSource.dita" navtitle="javax.sql.DataSource interface:
JDBC 3 and JDBC 4.0 features">
-</topicref>
-<topicref href="rrefjdbcrefsqlxml.dita" navtitle="java.sql.SQLXML interface">
-</topicref>
-</topicref>
 <topicref collection-type="family" href="rrefjdbc4_1summary.dita" navtitle="Features supported
on JDBC 4.1 and above">
 <topicref href="rrefjdbc4_1connection.dita" navtitle="java.sql.Connection interface: JDBC
4.1 features">
 </topicref>
-<topicref href="rrefjdbc4_1datasource.dita" navtitle="java.sql.DataSource interface: JDBC
4.1 features">
-</topicref>
 </topicref>
 <topicref collection-type="family" href="rrefjdbc4_2summary.dita" navtitle="Features supported
on JDBC 4.2">
 <topicref href="rrefjdbc4_2compactprofiles.dita" navtitle="JDBC DataSource support for
Java SE 8 Compact Profiles"></topicref>

Modified: db/derby/docs/trunk/src/ref/rrefapi1003363.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefapi1003363.dita?rev=1567962&r1=1567961&r2=1567962&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefapi1003363.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefapi1003363.dita Thu Feb 13 15:56:38 2014
@@ -27,12 +27,6 @@ limitations under the License.
 <indexterm>org.apache.derby.jdbc.ClientConnectionPoolDataSource</indexterm>
 <indexterm>org.apache.derby.jdbc.ClientXADataSource</indexterm>
 <indexterm>org.apache.derby.jdbc.ClientDataSource</indexterm>
-<indexterm>org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource40</indexterm>
-<indexterm>org.apache.derby.jdbc.EmbeddedXADataSource40</indexterm>
-<indexterm>org.apache.derby.jdbc.EmbeddedDataSource40</indexterm>
-<indexterm>org.apache.derby.jdbc.ClientConnectionPoolDataSource40</indexterm>
-<indexterm>org.apache.derby.jdbc.ClientXADataSource40</indexterm>
-<indexterm>org.apache.derby.jdbc.ClientDataSource40</indexterm>
 <indexterm>org.apache.derby.jdbc.BasicEmbeddedConnectionPoolDataSource40</indexterm>
 <indexterm>org.apache.derby.jdbc.BasicEmbeddedXADataSource40</indexterm>
 <indexterm>org.apache.derby.jdbc.BasicEmbeddedDataSource40</indexterm>
@@ -49,20 +43,12 @@ limitations under the License.
 resource managers" in the <ph conref="../conrefs.dita#pub/citdevelop"></ph>,
and
 "Accessing the Network Server by using a DataSource object" in the
 <ph conref="../conrefs.dita#pub/citadmin"></ph>.</p>
-<p>Embedded environment, for applications running on JDK 5 or higher and
-using JDBC 3 and JDBC 4.0 methods:</p>
+<p>Embedded environment:</p>
 <ul>
 <li><i>org.apache.derby.jdbc.EmbeddedDataSource</i></li>
 <li><i>org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource</i></li>
 <li><i>org.apache.derby.jdbc.EmbeddedXADataSource</i></li>
 </ul>
-<p>Embedded environment, for applications running on JDK 6 or higher and using
-methods specific to JDBC 4.1 or JDBC 4.2:</p>
-<ul>
-<li><i>org.apache.derby.jdbc.EmbeddedDataSource40</i></li>
-<li><i>org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource40</i></li>
-<li><i>org.apache.derby.jdbc.EmbeddedXADataSource40</i></li>
-</ul>
 <p>Embedded environment, for applications using Java SE 8 Compact Profile 2
 or 3:</p>
 <ul>
@@ -70,20 +56,12 @@ or 3:</p>
 <li><i>org.apache.derby.jdbc.BasicEmbeddedConnectionPoolDataSource40</i></li>
 <li><i>org.apache.derby.jdbc.BasicEmbeddedXADataSource40</i></li>
 </ul>
-<p>Client-server environment, for applications running on JDK 5 or higher and
-using JDBC 3 and JDBC 4.0 methods:</p>
+<p>Client-server environment:</p>
 <ul>
 <li><i>org.apache.derby.jdbc.ClientDataSource</i></li>
 <li><i>org.apache.derby.jdbc.ClientConnectionPoolDataSource</i></li>
 <li><i>org.apache.derby.jdbc.ClientXADataSource</i></li>
 </ul>
-<p>Client-server environment, for applications running on JDK 6 or higher and
-using methods specific to JDBC 4.1 or JDBC 4.2:</p>
-<ul>
-<li><i>org.apache.derby.jdbc.ClientDataSource40</i></li>
-<li><i>org.apache.derby.jdbc.ClientConnectionPoolDataSource40</i></li>
-<li><i>org.apache.derby.jdbc.ClientXADataSource40</i></li>
-</ul>
 <p>Client-server environment, for applications using Java SE 8 Compact Profile
 2 or 3:</p>
 <ul>

Modified: db/derby/docs/trunk/src/ref/rrefjdbc15905.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc15905.dita?rev=1567962&r1=1567961&r2=1567962&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc15905.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc15905.dita Thu Feb 13 15:56:38 2014
@@ -33,7 +33,8 @@ does not support catalogs. Similarly, me
 <i>ResultSet</i> will always return <i>null</i> in that column.</p>
 <p>The <ph conref="../conrefs.dita#prod/productshortname"></ph> implementation
 of the <i>getColumns</i> method returns an empty <i>ResultSet</i>
if the
-table specified in the third argument is a SYNONYM.</p>
+table specified in the third argument is a SYNONYM. The method reports "YES" as
+the value of IS_AUTOINCREMENT if a column is generated.</p>
 <p>The <ph conref="../conrefs.dita#prod/productshortname"></ph> implementation
 of the <i>getResultSetHoldability</i> method returns
 <i>ResultSet.HOLD_CURSORS_OVER_COMMIT</i>.

Modified: db/derby/docs/trunk/src/ref/rrefjdbc16643.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc16643.dita?rev=1567962&r1=1567961&r2=1567962&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc16643.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc16643.dita Thu Feb 13 15:56:38 2014
@@ -33,7 +33,22 @@ The first exception is always the most s
 exceptions preceding those that are specific to <ph conref="../conrefs.dita#prod/productshortname"></ph>.
 For information on processing <i>SQLExceptions</i>, see "Working with <ph

 conref="../conrefs.dita#prod/productshortname"></ph> SQLExceptions in an application"
-in the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
+in the <ph conref="../conrefs.dita#pub/citdevelop"></ph>.</p>
+<p>Exceptions raised by <ph conref="../conrefs.dita#prod/productshortname"></ph>
+will generally be one of the refined subclasses of <i>SQLException</i>. These
+refined exceptions are raised under the conditions described by their respective
+API documentation.</p>
+<ul>
+<li><b>java.sql.SQLClientInfoException</b></li>
+<li><b>java.sql.SQLDataException</b></li>
+<li><b>java.sql.SQLFeatureNotSupportedException</b></li>
+<li><b>java.sql.SQLIntegrityConstraintViolationException</b></li>
+<li><b>java.sql.SQLInvalidAuthorizationSpecException</b></li>
+<li><b>java.sql.SQLSyntaxErrorException</b></li>
+<li><b>java.sql.SQLTransactionRollbackException</b></li>
+<li><b>java.sql.SQLTransientConnectionException</b></li>
+</ul>
+</section>
 </refbody>
 </reference>
 

Modified: db/derby/docs/trunk/src/ref/rrefjdbc32052.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc32052.dita?rev=1567962&r1=1567961&r2=1567962&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc32052.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc32052.dita Thu Feb 13 15:56:38 2014
@@ -22,7 +22,6 @@ limitations under the License.
 <prolog><metadata>
 <keywords><indexterm>java.sql.Driver interface</indexterm>
 <indexterm>JDBC driver<indexterm>loading</indexterm></indexterm>
-<indexterm>jdbc.drivers system property<indexterm>using to load driver</indexterm></indexterm>
 </keywords>
 </metadata></prolog>
 <refbody>
@@ -30,39 +29,21 @@ limitations under the License.
 local JDBC driver is the class <i>org.apache.derby.jdbc.EmbeddedDriver</i>.
 The class that loads <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
 network client driver is the class <i>org.apache.derby.jdbc.ClientDriver</i>.
-Listed below are some of the ways to create instances of these classes. Do not use the classes
directly through the <i>java.sql.Driver</i> interface.
-Use the <i>DriverManager</i> class to create connections.</p>  
-<p>If your application runs on JDK 6 or higher, you do not need to
-do any of the following. The driver will load automatically
-when your application asks for its first connection.</p>
-<ul>
-<li><pre id="jdbc10841">Class.forName("org.apache.derby.jdbc.EmbeddedDriver");
-Class.forName("org.apache.derby.jdbc.ClientDriver");</pre>
-<p>The recommended way to load the driver class.</p>
-<p>With the embedded driver, if your application shuts down Derby or calls the
+Usually, you will not need to create instances of these classes, because the
+appropriate class is loaded automatically when your application requests a
+connection using the <i>DriverManager</i> class. This section describes a few
+exceptions to this rule.</p>
+<p>With the embedded driver, if your application shuts down
+<ph conref="../conrefs.dita#prod/productshortname"></ph> or calls the
 <i>DriverManager.deregisterDriver</i> method, and you then want to reload the
 driver, call the <i>Class.forName().newInstance()</i> method to do so:</p>
-<pre>Class.forName("org.apache.derby.jdbc.EmbeddedDriver").newInstance();</pre>
-</li>
-<li><pre>new org.apache.derby.jdbc.EmbeddedDriver();
-new org.apache.derby.jdbc.ClientDriver();</pre>   <p>Same as using
-<i>Class.forName()</i>, except
-that it requires the class to be found when the code is compiled.</p></li>
-<li><pre>Class c = org.apache.derby.jdbc.EmbeddedDriver.class;
-Class c = org.apache.derby.jdbc.ClientDriver.class;</pre>   <p>This
-is also the same as using <i>Class.forName()</i>, except
-that it requires the class to be found when the code is compiled. The pseudo-static
-field <i>class</i> evaluates to the class that is named.</p></li>
-<li><i>Setting the system property jdbc.drivers</i> 
- <p>To set a system property, you alter the invocation command line or the
-system properties within your application. It is not possible to alter system
-properties within an applet.</p>
-<codeblock>java -Djdbc.drivers=org.apache.derby.jdbc.EmbeddedDriver
-    applicationClass
-
-java -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-    applicationClass</codeblock></li>
-</ul></section>
+<codeblock>Class.forName("org.apache.derby.jdbc.EmbeddedDriver").newInstance();</codeblock>
+<p>You also need to call the <i>Class.forName</i> method in this way if
you need
+to load a non-default driver -- for example, if you want to load the embedded
+driver when using the Network Server. See, for example, "Overview of the
+SimpleNetworkServer Sample program" in the
+<ph conref="../conrefs.dita#pub/citadmin"></ph>.</p>
+</section>
 <section><p>The actual driver that gets registered in the <i>DriverManager</i>
to
 handle the <i>jdbc:derby:</i> protocol is not the class <i>org.apache.derby.jdbc.EmbeddedDriver</i>
 or <i>org.apache.derby.jdbc.ClientDriver</i>;
@@ -72,6 +53,6 @@ to be loaded.</p></section>
 <section><p>The only supported way to connect to a <ph conref="../conrefs.dita#prod/productshortname"></ph>
system
 through the <i>jdbc:derby:</i> protocol is using the <i>DriverManager</i>
to
 obtain a driver (<i>java.sql.Driver</i>) or connection (<i>java.sql.Connection</i>)
-through the <i>getDriver</i> and <i>getConnection</i> method calls.</p></section>
+through a <i>getDriver</i> or <i>getConnection</i> method call.</p></section>
 </refbody>
 </reference>

Modified: db/derby/docs/trunk/src/ref/rrefjdbc4_1summary.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc4_1summary.dita?rev=1567962&r1=1567961&r2=1567962&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc4_1summary.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc4_1summary.dita Thu Feb 13 15:56:38 2014
@@ -32,10 +32,10 @@ limitations under the License.
 documents the JDBC 4.1 features supported by
 <ph conref="../conrefs.dita#prod/productshortname"></ph>.</p>
 <p>For information on features supported by all releases of JDBC 4, see
-<xref href="rrefjdbc4_0summary.dita#rrefjdbc4_0summary"></xref>. For information
+<xref href="crefjdbc12657.dita#crefjdbc12657"></xref>. For information
 about features supported only by JDBC 4.2, see
 <xref href="rrefjdbc4_2summary.dita#rrefjdbc4_2summary"></xref>.</p>
-<p><note>JDBC 4.1 features are present only in a JDK 6 or higher
+<p><note>JDBC 4.1 features are present only in a JDK 7 or higher
 environment.</note></p>
 </section>
 </refbody>

Modified: db/derby/docs/trunk/src/ref/rrefjdbc4_2summary.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc4_2summary.dita?rev=1567962&r1=1567961&r2=1567962&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc4_2summary.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc4_2summary.dita Thu Feb 13 15:56:38 2014
@@ -31,7 +31,7 @@ limitations under the License.
 documents the JDBC 4.2 features supported by
 <ph conref="../conrefs.dita#prod/productshortname"></ph>.</p>
 <p>For information on features supported by all versions of JDBC 4, see
-<xref href="rrefjdbc4_0summary.dita#rrefjdbc4_0summary"></xref>. For information
+<xref href="crefjdbc12657.dita#crefjdbc12657"></xref>. For information
 on features supported by both JDBC 4.1 and JDBC 4.2, see
 <xref href="rrefjdbc4_1summary.dita#rrefjdbc4_1summary"></xref>.</p>
 <p><note>JDBC 4.2 features are present only in a JDK 8 or higher

Modified: db/derby/docs/trunk/src/ref/rrefjdbcrefsqlxml.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbcrefsqlxml.dita?rev=1567962&r1=1567961&r2=1567962&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbcrefsqlxml.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbcrefsqlxml.dita Thu Feb 13 15:56:38 2014
@@ -24,15 +24,15 @@ limitations under the License.
 <keywords><indexterm>java.sql.SQLXML interface</indexterm></keywords>
 </metadata></prolog>
 <refbody>
-<section><p>In JDBC 4.0, java.sql.SQLXML is the mapping for the SQL XML data
+<section><p>The <i>java.sql.SQLXML</i> interface is the mapping for
the SQL XML data
 type.  However, <ph conref="../conrefs.dita#prod/productshortname"></ph> defines
 the XML data type and operators only in the SQL layer. There is no JDBC-side
-support for the XML data type and operators</p><p>You cannot instantiate a
-java.sql.SQLXML object in <ph conref="../conrefs.dita#prod/productshortname"></ph>,
+support for the XML data type and operators.</p><p>You cannot instantiate a
+<i>java.sql.SQLXML</i> object in <ph conref="../conrefs.dita#prod/productshortname"></ph>,
 or bind directly into an XML value or retrieve an XML value directly from
 a result set.  You must bind and retrieve the XML data as Java strings or
 character streams by explicitly specifying the XML operators, XMLPARSE and
 XMLSERIALIZE, as part of your SQL queries. </p><p>Additionally, <ph conref="../conrefs.dita#prod/productshortname"></ph>
does
-not provide JDBC metatadata support for the XML data type. </p></section>
+not provide JDBC metadata support for the XML data type.</p></section>
 </refbody>
 </reference>

Modified: db/derby/docs/trunk/src/ref/rrefjta18596.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjta18596.dita?rev=1567962&r1=1567961&r2=1567962&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjta18596.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjta18596.dita Thu Feb 13 15:56:38 2014
@@ -21,8 +21,8 @@ limitations under the License.
 <reference id="rrefjta18596" xml:lang="en-us">
 <title>javax.sql: JDBC Interfaces</title>
 <prolog><metadata>
-<keywords><indexterm>javax.sql package</indexterm><indexterm>JDBC
2.0<indexterm>standard
-interfaces</indexterm></indexterm><indexterm>javax.sql.PooledConnection</indexterm>
+<keywords><indexterm>javax.sql package</indexterm>
+<indexterm>javax.sql.PooledConnection</indexterm>
 <indexterm>Connection pooling</indexterm><indexterm>javax.sql.DataSource</indexterm>
 <indexterm>Data sources</indexterm><indexterm>javax.sql.XAConnection</indexterm>
 <indexterm>javax.sql.XADataSource</indexterm><indexterm>Data sources<indexterm>creating
@@ -43,16 +43,16 @@ with a naming service based on the Java 
 <codeph>org.apache.derby.jdbc</codeph> DataSource classes support the JNDI API,
 with the exception of the DataSource classes that support Java SE 8 Compact
 Profiles 2 and 3. See
-<xref href="rrefjdbc4_0dataSource.dita#rrefjdbc4_0dataSource"></xref>,
-<xref href="rrefjdbc4_1datasource.dita#rrefjdbc4_1datasource"></xref>, and
+<xref href="rrefapi1003363.dita#rrefapi1003363"></xref> and
 <xref href="rrefjdbc4_2compactprofiles.dita#rrefjdbc4_2compactprofiles"></xref>
 for more information.</p></li>
 <li><i id="jta96573">javax.sql.ConnectionPoolDataSource</i>  and <i>
javax.sql.PooledConnection</i>  <p>Establishing
 a connection to the database can be a relatively expensive operation in client/server
 environments. Establishing the connection once and then using the same connection
 for multiple requests can dramatically improve the performance of a database.</p> <p>The
<ph
-conref="../conrefs.dita#prod/productshortname"></ph> implementation of <codeph>ConnectionPoolDataSource</codeph>
and <codeph>PooledConnection</codeph
-> interfaces allows a connection pool server to maintain a set of such connections
+conref="../conrefs.dita#prod/productshortname"></ph> implementation of the
+<codeph>ConnectionPoolDataSource</codeph> and <codeph>PooledConnection</codeph>
+interfaces allows a connection pool server to maintain a set of such connections
 to the resource manager (<ph conref="../conrefs.dita#prod/productshortname"></ph>).
 In an embedded environment, connections are much cheaper and connection pooling
 is not necessary.</p></li>



Mime
View raw message