db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1569055 - in /db/derby/docs/trunk/src: adminguide/cadminjmxoverview.dita ref/rrefattribderegister.dita ref/rrefexcept16677.dita ref/rrefjavsqlprst.dita ref/rrefproperdefaultfileperms.dita
Date Mon, 17 Feb 2014 16:47:43 GMT
Author: chaase3
Date: Mon Feb 17 16:47:42 2014
New Revision: 1569055

URL: http://svn.apache.org/r1569055
DERBY-6236  Oracle Java documentation URLs need updating

Modified 1 Admin Guide and 4 Reference Manual topics.

Patch: DERBY-6236-more.diff


Modified: db/derby/docs/trunk/src/adminguide/cadminjmxoverview.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminjmxoverview.dita?rev=1569055&r1=1569054&r2=1569055&view=diff
--- db/derby/docs/trunk/src/adminguide/cadminjmxoverview.dita (original)
+++ db/derby/docs/trunk/src/adminguide/cadminjmxoverview.dita Mon Feb 17 16:47:42 2014
@@ -47,8 +47,8 @@ security features to enable this access.
 <p>The <ph conref="../conrefs.dita#prod/productshortname"></ph> JMX features
 automatically available when
 <ph conref="../conrefs.dita#prod/productshortname"></ph> is started in a JVM
-that supports the platform MBean server. Java SE 5 and subsequent releases all
-support JMX technology.</p>
+that supports the platform MBean server. Most versions of the Java SE platform
+support JMX technology (Java SE 8 Compact Profile 2, for example, does not).</p>
 <p>You start <ph conref="../conrefs.dita#prod/productshortname"></ph> by
 the <ph conref="../conrefs.dita#prod/productshortname"></ph> embedded driver.
 you are using the <ph conref="../conrefs.dita#prod/productshortname"></ph>

Modified: db/derby/docs/trunk/src/ref/rrefattribderegister.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefattribderegister.dita?rev=1569055&r1=1569054&r2=1569055&view=diff
--- db/derby/docs/trunk/src/ref/rrefattribderegister.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefattribderegister.dita Mon Feb 17 16:47:42 2014
@@ -44,21 +44,16 @@ deregistered:</p>
 this permission when using a security manager, an error message and stack trace
 will appear in <i>derby.log</i> on shutdown, and the embedded JDBC driver
 will remain registered.</p>
-<p>If you are running with a security manager on JDK 7 or earlier, you do not
+<p>If you are running with a security manager on JDK 6 or 7, you do not
 need to set this permission.</p> 
 <p>You initially register the embedded driver by doing one of the following:</p>
-<li>Call the method
-This mechanism works on all supported Java Virtual Machines (JVMs) (that is,
-JDK 5 and up).</li>
+<li>Call the method <i>DriverManager.getConnection()</i>.</li>
 <li>Set <i>-Djdbc.drivers=org.apache.derby.jdbc.EmbeddedDriver</i> when
 boot the <ph conref="../conrefs.dita#prod/productshortname"></ph> engine's VM,
 then call
 <i><xref href="rrefjdbc34565.dita#rrefjdbc34565">DriverManager.getConnection()</xref></i>.
-This mechanism also works on all supported JVMs.</li>
-<li>Simply call <i>DriverManager.getConnection()</i>. This mechanism works
-on JDK 6 and up.</li>
 <p>Once the embedded driver is registered, you can shut down the
 <ph conref="../conrefs.dita#prod/productshortname"></ph> engine by using the
@@ -70,9 +65,7 @@ shutdown URL, the following will happen:
 <li>The <ph conref="../conrefs.dita#prod/productshortname"></ph> classes
 <b>not</b> be garbage-collected.</li>
 <li>You can get a <ph conref="../conrefs.dita#prod/productshortname"></ph>
-connection just by issuing a call to <i>DriverManager.getConnection()</i>. That
-is, you <b>do not</b> need to first call
+connection by issuing a call to <i>DriverManager.getConnection()</i>.</li>
 <p>In contrast, if you use the default setting of <i>deregister=true</i>
 you shut down the database, the following will happen:</p>
@@ -83,7 +76,7 @@ garbage-collected.</li>
 <li>You will have to call
 <i>Class.forName("org.apache.derby.jdbc.EmbeddedDriver").newInstance()</i> before
 you obtain a new <ph conref="../conrefs.dita#prod/productshortname"></ph>
+connection by calling <i>DriverManager.getConnection()</i>.</li>
 <p>This attribute has no meaning if it is used with the network driver.</p>

Modified: db/derby/docs/trunk/src/ref/rrefexcept16677.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefexcept16677.dita?rev=1569055&r1=1569054&r2=1569055&view=diff
--- db/derby/docs/trunk/src/ref/rrefexcept16677.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefexcept16677.dita Mon Feb 17 16:47:42 2014
@@ -31,8 +31,7 @@ are returned for exceptions where approp
 <section><p>Unimplemented aspects of the JDBC driver return a <i>SQLException</i>
-a <i>SQLState</i> starting with <codeph>0A</codeph>. If your
-application runs on JDK 1.6 or higher, then the exception class is
+a <i>SQLState</i> starting with <codeph>0A</codeph>. The exception
class is
 These unimplemented parts are for features not supported by <ph conref="../conrefs.dita#prod/productshortname"></ph>.</p></section>
 <section><p><ph conref="../conrefs.dita#prod/productshortname"></ph>

Modified: db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita?rev=1569055&r1=1569054&r2=1569055&view=diff
--- db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita Mon Feb 17 16:47:42 2014
@@ -44,15 +44,10 @@ the following JDBC stream methods for <i
 <note><ph conref="../conrefs.dita#prod/productshortname"></ph> does not
 the <i>setNCharacterStream</i> method or the deprecated <i>setUnicodeStream</i>
-<p>JDBC 3.0 requires that you specify the length of the
-stream, and <ph conref="../conrefs.dita#prod/productshortname"></ph> enforces
-this requirement if your application runs on JDK 5. If your application
-runs on JDK 6 or later, <ph conref="../conrefs.dita#prod/productshortname"></ph>
-exposes a JDBC 4.0 implementation, which lets you use the streaming interfaces
-without having to specify the stream length.</p>
-<p><note>If you omit the length argument when the stream object is a LOB greater
-than a single page in size, performance will be impaired if you later retrieve
-the length of the LOB. However, if you are simply inserting or reading data,
+<p><note>These methods do not require that you specify the length of the
+stream. However, if you omit the length argument when the stream object is a LOB
+greater than a single page in size, performance will be impaired if you later
+retrieve the length of the LOB. If you are simply inserting or reading data,
 performance is unaffected.</note></p>
 <p>The stream object passed to <i>setBinaryStream</i> and <i>setAsciiStream</i>
 can be either a standard Java stream object or the user's own subclass that

Modified: db/derby/docs/trunk/src/ref/rrefproperdefaultfileperms.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefproperdefaultfileperms.dita?rev=1569055&r1=1569054&r2=1569055&view=diff
--- db/derby/docs/trunk/src/ref/rrefproperdefaultfileperms.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefproperdefaultfileperms.dita Mon Feb 17 16:47:42 2014
@@ -38,7 +38,7 @@ servers that are started programmaticall
 <ph conref="../conrefs.dita#prod/productshortname"></ph> API.</p>
 <p>You can override this default behavior by setting the system property
 <i>derby.storage.useDefaultFilePermissions</i> to either true or false:</p>
-<p>If you use a version of Java SE earlier than Java SE 7, this property is
+<p>If you run with the Java SE 6 platform, this property is
 ignored, and <ph conref="../conrefs.dita#prod/productshortname"></ph> uses the
 default file permissions the user has set for their system.</p>
 <p>The two tables that follow show how file access works with Java SE 6 and with

View raw message