db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r732111 - /db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita
Date Tue, 06 Jan 2009 20:48:09 GMT
Author: chaase3
Date: Tue Jan  6 12:48:09 2009
New Revision: 732111

URL: http://svn.apache.org/viewvc?rev=732111&view=rev
Log:
DERBY-3983: User Guide documentation on the limitations of small-device support is stale

This patch updates the information in the Reference Manual topic on JSR 169 support, "JDBC
Package for Connected Device Configuration/Foundation Profile (JSR 169)", and organizes it
more usefully.

Patch: DERBY-3983-2.diff

Modified:
    db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita

Modified: db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita?rev=732111&r1=732110&r2=732111&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita Tue Jan  6 12:48:09 2009
@@ -19,37 +19,61 @@
 -->
 <reference id="rrefjdbcjsr169" xml:lang="en-us">
 <title>JDBC Package for Connected Device Configuration/Foundation Profile
-(JSR169)</title>
+(JSR 169)</title>
 <prolog><metadata>
-<keywords><indexterm>JSR169-only features<indexterm>Derby's support for</indexterm></indexterm>
+<keywords><indexterm>JSR 169 features<indexterm>support for</indexterm></indexterm>
 </keywords>
 </metadata></prolog>
 <refbody>
 <section><p><ph conref="../conrefs.dita#prod/productshortname"></ph>
supports
 the JDBC API defined for the Connected Device Configuration/Foundation Profile,
-also known as JSR169. The features supported are a subset of the JDBC 3.0
-specification. Support for JSR169 is limited to the embedded driver. <ph conref="../conrefs.dita#prod/productshortname"></ph>
does
-not support using the Network Server under JSR169.</p></section>
-<section><p>To obtain a connection under JSR169 specifications, use the <codeph>org.apache.derby.jdbc.EmbeddedSimpleDataSource</codeph>
class.
+also known as JSR 169. The features supported are a subset of the JDBC 3.0
+specification. Support for JSR 169 is limited to the embedded driver.
+<ph conref="../conrefs.dita#prod/productshortname"></ph> does not support using
+the Network Server under JSR 169.</p></section>
+<section><p>To obtain a connection using JSR 169, use the
+<codeph>org.apache.derby.jdbc.EmbeddedSimpleDataSource</codeph> class.
 This class is identical in implementation to the <codeph>org.apache.derby.jdbc.EmbeddedDataSource</codeph>
class.
 See the <ph conref="../conrefs.dita#pub/citdevelop"></ph> for information
-on using the properties of the <codeph>org.apache.derby.jdbc.EmbeddedDataSource</codeph>
class.</p><p>Some
-other features to note concerning the JSR169 implementation using <ph conref="../conrefs.dita#prod/productshortname"></ph>:<ul>
+on using the properties of the <codeph>org.apache.derby.jdbc.EmbeddedDataSource</codeph>
class.</p>
+<p>JSR 169 and its <ph conref="../conrefs.dita#prod/productshortname"></ph>
+implementation have the following limitations:</p>
+<ul>
 <li>Applications must get and set <codeph>DECIMAL</codeph> values using
alternate
 JDBC <codeph>getXXX</codeph> and <codeph>setXXX</codeph> methods,
such as <codeph>getString()</codeph> and <codeph>setString()</codeph>.
-Any alternate method that works against a DECIMAL type with JDBC 2.0 or 3.0
-will work in JSR169.</li>
-<li>Java functions and procedures that use server-side JDBC parameters such
-as <codeph>CONTAINS SQL</codeph>, <codeph>READS SQL DATA</codeph>
or <codeph>MODIFIES
-SQL DATA</codeph> are not supported in JSR169.</li>
-<li>The standard API used to obtain a connection (<codeph>jdbc:default:connection</codeph>)
-is not supported in JSR169. A runtime error may occur when the routine tries
-to obtain a connection using <codeph>jdbc:default:connection</codeph>.</li>
-<li>Diagnostic tables are not supported.</li>
-<li>Triggers are not supported.</li>
-<li>Encrypted databases are not supported.</li>
-<li>DriverManager is not supported. You cannot use DriverManager.getConnection()
-to obtain a connection.</li>
-</ul></p></section>
+Any alternate method that works against a DECIMAL type with JDBC 3.0
+will work in JSR 169.</li>
+<li>The XML data type is not supported, but an application can retrieve, update,
+query, or otherwise access an XML data value if it has 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)</li>
+</ul>
+<p>JSR 169 and its <ph conref="../conrefs.dita#prod/productshortname"></ph>
+implementation do not support the following:</p>
+<ul>
+<li>Java functions and procedures that use server-side JDBC, that is, routines
+declared with <codeph>CONTAINS SQL</codeph>, <codeph>READS SQL DATA</codeph>,
+or <codeph>MODIFIES SQL DATA</codeph> clauses</li>
+<li>The <codeph>DriverManager</codeph> interface (this means that you cannot
use
+the <codeph>DriverManager.getConnection</codeph> method to obtain
+a connection but must use the
+<codeph>org.apache.derby.jdbc.EmbeddedSimpleDataSource</codeph> class instead)
+</li>
+<li>The standard URL used to obtain a connection,
+<codeph>jdbc:default:connection</codeph> (a runtime error may occur if the
+routine tries to obtain a connection using
+<codeph>jdbc:default:connection</codeph>)</li>
+<li>Diagnostic tables</li>
+<li>Triggers</li>
+<li>Encrypted databases</li>
+<li>Non-blocking I/O</li>
+<li>Java EE resource manager support, including distributed transactions</li>
+<li>Principal-based security</li>
+<li>LDAP-based authentication</li>
+<li>SSL/TLS encryption</li>
+<li>Replication</li>
+</ul>
+</section>
 </refbody>
 </reference>



Mime
View raw message