You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openjpa.apache.org by mt...@apache.org on 2011/09/21 20:48:25 UTC

svn commit: r1173790 - in /openjpa/trunk/openjpa-project/src/doc/manual: migration_considerations.xml ref_guide_dbsetup.xml

Author: mtylenda
Date: Wed Sep 21 18:48:24 2011
New Revision: 1173790

URL: http://svn.apache.org/viewvc?rev=1173790&view=rev
Log:
OPENJPA-1691: Documentation update - be more specific about OpenJPA versions, improve formatting.

Modified:
    openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml
    openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml

Modified: openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml?rev=1173790&r1=1173789&r2=1173790&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml Wed Sep 21 18:48:24 2011
@@ -433,18 +433,18 @@
                     </itemizedlist>    
                 </para>
             </section>
-            <section id="SupportsSetClob">
+            <section id="jpa_2.2_SupportsSetClob">
                 <title>
-                    supportsSetClob property.  
+                    supportsSetClob Property.  
                 </title>
                 <!-- See OPENJPA-1691 for details. -->
                 <para>
-                    In the OpenJPA 2.1.x release, code was added to OpenJPA to allow the setting of Clob or XML data larger than 4000 bytes.  This functionality
-                    was eventually back ported to previous releases, and enabeld by the supportsSetClob property on the OracleDictionary.  Setting this property 
-                    has no effect in 2.1.x and later releases and any occurrence of it should be removed.
+                    In OpenJPA 2.2.0, code was added to allow the setting of CLOB or XML data larger than 4000 bytes.  This functionality
+                    was eventually back ported to previous releases, and enabled by the <literal>supportsSetClob</literal> property on the OracleDictionary.  Setting this property 
+                    has no effect in 2.2.0 and later releases and any occurrence of it should be removed.
                 </para>
             </section>            
-            <section id="UseNativeSequenceCache">
+            <section id="jpa_2.2_UseNativeSequenceCache">
                 <title>
                     useNativeSequenceCache Property.  
                 </title>

Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml?rev=1173790&r1=1173789&r2=1173790&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml Wed Sep 21 18:48:24 2011
@@ -3888,10 +3888,11 @@ CLOB to persist with the embedded method
                 </listitem>
                 <listitem id="OracleDictionary.SupportsSetClob">
                     <para>
-<literal>SupportsSetClob</literal>: This property was used in previous releases 
+<literal>SupportsSetClob</literal>: This property was used in releases previous
+to OpenJPA 2.2.0
 to indicate that OpenJPA should attempt to use a Reader-based JDBC 4.0 method to 
-set Clob or XML data.  It allowed XMLType and Clob values larger than 4000 bytes 
-to be used.  For this release, and newer, code was added to allow said 
+set CLOB or XML data.  It allowed XMLType and CLOB values larger than 4000 bytes 
+to be used.  For OpenJPA 2.2.0 and later releases, code was added to allow said 
 functionality by default (see OPENJPA-1691).  For forward compatibility, this 
 property still remains, however it has been deprecated and will eventually be
 removed.  Setting this property has no effect and any occurrence of it should