openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kwsut...@apache.org
Subject svn commit: r908837 [26/37] - /websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/
Date Wed, 14 May 2014 22:22:26 GMT
Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_dbsupport.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_isolation.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_isolation.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_isolation.html Wed May 14 22:22:23 2014
@@ -0,0 +1,64 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>5.&nbsp; Setting the Transaction Isolation</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide_dbsetup.html" title="Chapter&nbsp;4.&nbsp; JDBC"><link rel="prev" href="ref_guide_dbsetup_dbsupport.html" title="4.&nbsp; Database Support"><link rel="next" href="ref_guide_dbsetup_sql92.html" title="6.&nbsp; Setting the SQL Join Syntax"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.&nbsp;
+            Setting the Transaction Isolation
+        </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_dbsetup_dbsupport.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;4.&nbsp;
+        JDBC
+    </th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_sql92.html">Next</a></td></tr></table><hr></div><div class="section" title="5.&nbsp; Setting the Transaction Isolation"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="ref_guide_dbsetup_isolation">5.&nbsp;
+            Setting the Transaction Isolation
+        </h2></div></div></div>
+        
+        <a class="indexterm" name="d5e11401"></a>
+        <a class="indexterm" name="d5e11404"></a>
+        <a class="indexterm" name="d5e11407"></a>
+        <p>
+OpenJPA typically retains the default transaction isolation level of the JDBC
+driver. However, you can specify a transaction isolation level to use through
+the <a class="link" href="ref_guide_conf_jdbc.html#openjpa.jdbc.TransactionIsolation" title="6.18.&nbsp; openjpa.jdbc.TransactionIsolation"><code class="literal">
+openjpa.jdbc.TransactionIsolation</code></a> configuration property. The
+following is a list of standard isolation levels. Note that not all databases
+support all isolation levels.
+        </p>
+        <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+                <p>
+<code class="literal">default</code>: Use the JDBC driver's default isolation level.
+OpenJPA uses this option if you do not explicitly specify any other.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">none</code>: No transaction isolation.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">read-committed</code>: Dirty reads are prevented; non-repeatable
+reads and phantom reads can occur.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">read-uncommitted</code>: Dirty reads, non-repeatable reads and
+phantom reads can occur.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">repeatable-read</code>: Dirty reads and non-repeatable reads are
+prevented; phantom reads can occur.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">serializable</code>: Dirty reads, non-repeatable reads, and phantom
+reads are prevented.
+                </p>
+            </li></ul></div>
+        <div class="example"><a name="ref_guide_dbsetup_isoex"></a><p class="title"><b>Example&nbsp;4.8.&nbsp;
+                Specifying a Transaction Isolation
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+&lt;property name="openjpa.jdbc.TransactionIsolation" value="repeatable-read"/&gt;
+</pre>
+        </div></div><br class="example-break">
+    </div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_dbsetup_dbsupport.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide_dbsetup.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_sql92.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.&nbsp;
+            Database Support
+        &nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;6.&nbsp;
+            Setting the SQL Join Syntax
+        </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_isolation.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_lrs.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_lrs.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_lrs.html Wed May 14 22:22:23 2014
@@ -0,0 +1,180 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>10.&nbsp; Large Result Sets</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide_dbsetup.html" title="Chapter&nbsp;4.&nbsp; JDBC"><link rel="prev" href="ref_guide_dbsetup_stmtbatch.html" title="9.&nbsp; Statement Batching"><link rel="next" href="ref_guide_schema_def.html" title="11.&nbsp; Default Schema"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">10.&nbsp;
+            Large Result Sets
+        </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_dbsetup_stmtbatch.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;4.&nbsp;
+        JDBC
+    </th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_schema_def.html">Next</a></td></tr></table><hr></div><div class="section" title="10.&nbsp; Large Result Sets"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="ref_guide_dbsetup_lrs">10.&nbsp;
+            Large Result Sets
+        </h2></div></div></div>
+        
+        <a class="indexterm" name="d5e11616"></a>
+        <a class="indexterm" name="d5e11618"></a>
+        <p>
+By default, OpenJPA uses standard forward-only JDBC result sets, and completely
+instantiates the results of database queries on execution. When using a JDBC
+driver that supports version 2.0 or higher of the JDBC specification, however,
+you can configure OpenJPA to use scrolling result sets that may not bring all
+results into memory at once. You can also configure the number of result objects
+OpenJPA keeps references to, allowing you to traverse potentially enormous
+amounts of data without exhausting JVM memory.
+        </p>
+        <div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
+            <p>
+You can also configure on-demand loading for individual collection and map
+fields via large result set proxies. See
+<a class="xref" href="ref_guide_pc_scos.html#ref_guide_pc_scos_proxy_lrs" title="6.4.2.&nbsp; Large Result Set Proxies">Section&nbsp;6.4.2, &#8220;
+                    Large Result Set Proxies
+                &#8221;</a>.
+            </p>
+        </div>
+        <p>
+Use the following properties to configure OpenJPA's handling of result sets:
+        </p>
+        <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+                <p>
+                <a class="indexterm" name="d5e11630"></a>
+<a class="link" href="ref_guide_conf_openjpa.html#openjpa.FetchBatchSize" title="5.33.&nbsp; openjpa.FetchBatchSize"><code class="literal">openjpa.FetchBatchSize</code>
+</a>: The number of objects to instantiate at once when traversing a result
+set. This number will be set as the fetch size on JDBC <code class="classname">Statement
+</code> objects used to obtain result sets. It also factors in to the
+number of objects OpenJPA will maintain a hard reference to when traversing a
+query result.
+                </p>
+                <p>
+The fetch size defaults to -1, meaning all results will be instantiated
+immediately on query execution. A value of 0 means to use the JDBC driver's
+default batch size. Thus to enable large result set handling, you must set this
+property to 0 or to a positive number.
+                </p>
+            </li><li class="listitem">
+                <p>
+                <a class="indexterm" name="d5e11638"></a>
+<a class="link" href="ref_guide_conf_jdbc.html#openjpa.jdbc.ResultSetType" title="6.11.&nbsp; openjpa.jdbc.ResultSetType"><code class="literal"> openjpa.jdbc.ResultSetType
+</code></a>: The type of result set to use when executing database
+queries. This property accepts the following values, each of which corresponds
+exactly to the same-named <code class="classname">java.sql.ResultSet</code> constant:
+                </p>
+                <div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem">
+                        <p>
+<code class="literal">forward-only</code>: This is the default.
+                        </p>
+                    </li><li class="listitem">
+                        <p>
+<code class="literal">scroll-sensitive</code>
+                        </p>
+                    </li><li class="listitem">
+                        <p>
+<code class="literal">scroll-insensitive</code>
+                        </p>
+                    </li></ul></div>
+                <p>
+Different JDBC drivers treat the different result set types differently. Not all
+drivers support all types.
+                </p>
+            </li><li class="listitem">
+                <p>
+                <a class="indexterm" name="d5e11656"></a>
+<a class="link" href="ref_guide_conf_jdbc.html#openjpa.jdbc.FetchDirection" title="6.5.&nbsp; openjpa.jdbc.FetchDirection"><code class="literal">
+openjpa.jdbc.FetchDirection</code></a>: The expected order in which you
+will access the query results. This property affects the type of data structure
+OpenJPA will use to hold the results, and is also given to the JDBC driver in
+case it can optimize for certain access patterns. This property accepts the
+following values, each of which corresponds exactly to the same-named
+<code class="classname">java.sql.ResultSet</code> FETCH constant:
+                </p>
+                <div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem">
+                        <p>
+<code class="literal">forward</code>: This is the default.
+                        </p>
+                    </li><li class="listitem">
+                        <p>
+<code class="literal">reverse</code>
+                        </p>
+                    </li><li class="listitem">
+                        <p>
+<code class="literal">unknown</code>
+                        </p>
+                    </li></ul></div>
+                <p>
+Not all drivers support all fetch directions.
+                </p>
+            </li><li class="listitem">
+                <p>
+                <a class="indexterm" name="d5e11674"></a>
+<a class="link" href="ref_guide_conf_jdbc.html#openjpa.jdbc.LRSSize" title="6.7.&nbsp; openjpa.jdbc.LRSSize"><code class="literal"> openjpa.jdbc.LRSSize</code>
+</a>: The strategy OpenJPA will use to determine the size of result sets.
+This property is <span class="bold"><strong>only</strong></span> used if you change the
+fetch batch size from its default of -1, so that OpenJPA begins to use on-demand
+result loading. Available values are:
+                </p>
+                <div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem">
+                        <p>
+<code class="literal">query</code>: This is the default. The first time you ask for the
+size of a query result, OpenJPA will perform a <code class="literal">SELECT COUNT(*)
+</code> query to determine the number of expected results. Note that
+depending on transaction status and settings, this can mean that the reported
+size is slightly different than the actual number of results available.
+                        </p>
+                    </li><li class="listitem">
+                        <p>
+<code class="literal">last</code>: If you have chosen a scrollable result set type, this
+setting will use the <code class="methodname">ResultSet.last</code> method to move to
+the last element in the result set and get its index. Unfortunately, some JDBC
+drivers will bring all results into memory in order to access the last one. Note
+that if you do not choose a scrollable result set type, then this will behave
+exactly like <code class="literal">unknown</code>. The default result set type is
+<code class="literal">forward-only</code>, so you must change the result set type in
+order for this property to have an effect.
+                        </p>
+                    </li><li class="listitem">
+                        <p>
+<code class="literal">unknown</code>: Under this setting OpenJPA will return <code class="literal">
+Integer.MAX_VALUE</code> as the size for any query result that uses on-demand
+loading.
+                        </p>
+                    </li></ul></div>
+            </li></ul></div>
+        <div class="example"><a name="ref_guide_dbsetup_lrs_def"></a><p class="title"><b>Example&nbsp;4.16.&nbsp;
+                Specifying Result Set Defaults
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+&lt;property name="openjpa.FetchBatchSize" value="20"/&gt;
+&lt;property name="openjpa.jdbc.ResultSetType" value="scroll-insensitive"/&gt;
+&lt;property name="openjpa.jdbc.FetchDirection" value="forward"/&gt;
+&lt;property name="openjpa.jdbc.LRSSize" value="last"/&gt;
+</pre>
+        </div></div><br class="example-break">
+        <p>
+Many <a class="link" href="ref_guide_runtime.html" title="Chapter&nbsp;9.&nbsp; Runtime Extensions">OpenJPA runtime components</a> also
+have methods to configure these properties on a case-by-case basis through their
+fetch configuration. See <a class="xref" href="ref_guide_runtime.html" title="Chapter&nbsp;9.&nbsp; Runtime Extensions">Chapter&nbsp;9, <i>
+        Runtime Extensions
+    </i></a>.
+        </p>
+        <div class="example"><a name="ref_guide_dbsetup_lrs_runtime"></a><p class="title"><b>Example&nbsp;4.17.&nbsp;
+                Specifying Result Set Behavior at Runtime
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+import java.sql.*;
+import org.apache.openjpa.persistence.jdbc.*;
+
+...
+
+Query q = em.createQuery("select m from Magazine m where m.title = 'JDJ'");
+OpenJPAQuery kq = OpenJPAPersistence.cast(q);
+JDBCFetchPlan fetch = (JDBCFetchPlan) kq.getFetchPlan();
+fetch.setFetchBatchSize(20);
+fetch.setResultSetType(ResultSetType.SCROLL_INSENSITIVE);
+fetch.setFetchDirection(FetchDirection.FORWARD);
+fetch.setLRSSizeAlgorithm(LRSSizeAlgorithm.LAST);
+List results = q.getResultList();
+</pre>
+        </div></div><br class="example-break">
+    </div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_dbsetup_stmtbatch.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide_dbsetup.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_schema_def.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">9.&nbsp;
+            Statement Batching
+        &nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;11.&nbsp;
+            Default Schema
+        </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_lrs.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_multidb.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_multidb.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_multidb.html Wed May 14 22:22:23 2014
@@ -0,0 +1,24 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>7.&nbsp; Accessing Multiple Databases</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide_dbsetup.html" title="Chapter&nbsp;4.&nbsp; JDBC"><link rel="prev" href="ref_guide_dbsetup_sql92.html" title="6.&nbsp; Setting the SQL Join Syntax"><link rel="next" href="ref_guide_dbsetup_retain.html" title="8.&nbsp; Configuring the Use of JDBC Connections"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">7.&nbsp;
+            Accessing Multiple Databases
+        </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_dbsetup_sql92.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;4.&nbsp;
+        JDBC
+    </th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_retain.html">Next</a></td></tr></table><hr></div><div class="section" title="7.&nbsp; Accessing Multiple Databases"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="ref_guide_dbsetup_multidb">7.&nbsp;
+            Accessing Multiple Databases
+        </h2></div></div></div>
+        
+        <a class="indexterm" name="d5e11469"></a>
+        <p>
+Through the properties we've covered thus far, you can configure each 
+<code class="classname">EntityManagerFactory</code> to access a different
+database. If your application accesses multiple databases, we recommend that you
+maintain a separate persistence unit for each one. This will allow you to easily
+load the appropriate resource for each database at runtime, and to give the
+correct configuration file to OpenJPA's command-line tools during development.
+        </p>
+    </div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_dbsetup_sql92.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide_dbsetup.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_retain.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.&nbsp;
+            Setting the SQL Join Syntax
+        &nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;8.&nbsp;
+            Configuring the Use of JDBC Connections
+        </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_multidb.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_retain.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_retain.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_retain.html Wed May 14 22:22:23 2014
@@ -0,0 +1,201 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>8.&nbsp; Configuring the Use of JDBC Connections</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide_dbsetup.html" title="Chapter&nbsp;4.&nbsp; JDBC"><link rel="prev" href="ref_guide_dbsetup_multidb.html" title="7.&nbsp; Accessing Multiple Databases"><link rel="next" href="ref_guide_dbsetup_stmtbatch.html" title="9.&nbsp; Statement Batching"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">8.&nbsp;
+            Configuring the Use of JDBC Connections
+        </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_dbsetup_multidb.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;4.&nbsp;
+        JDBC
+    </th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_stmtbatch.html">Next</a></td></tr></table><hr></div><div class="section" title="8.&nbsp; Configuring the Use of JDBC Connections"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="ref_guide_dbsetup_retain">8.&nbsp;
+            Configuring the Use of JDBC Connections
+        </h2></div></div></div>
+        
+        <a class="indexterm" name="d5e11476"></a>
+        <p>
+In its default configuration, OpenJPA obtains JDBC connections on an as-needed
+basis. OpenJPA <code class="classname">EntityManager</code>s do not retain a connection
+to the database unless they are in a datastore transaction or there are open
+<code class="classname">Query</code> results that are using a live JDBC result set. At
+all other times, including during optimistic transactions, <code class="classname">
+EntityManager</code>s request a connection for each query, then
+immediately release the connection back to the pool.
+        </p>
+        <p>
+        <a class="indexterm" name="d5e11484"></a>
+In some cases, it may be more efficient to retain connections for longer periods
+of time. You can configure OpenJPA's use of JDBC connections through the
+<a class="link" href="ref_guide_conf_openjpa.html#openjpa.ConnectionRetainMode" title="5.25.&nbsp; openjpa.ConnectionRetainMode"><code class="literal">
+openjpa.ConnectionRetainMode</code></a> configuration property. The
+property accepts the following values:
+        </p>
+        <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+                <p>
+<code class="literal">always</code>: Each <code class="classname">EntityManager</code> obtains a
+single connection and uses it until the <code class="classname">EntityManager</code>
+closes. Great care should be taken when using this property if the application 
+cannot close the EntityManager (i.e. container-managed EntityManagers in a JEE 
+Application Server). In this case the connection will remain open for an 
+undefined time and the application may not be able to recover from a terminated
+connection (for example, if a TCP/IP timeout severs the connection to the database). 
+For this reason the <code class="literal">always</code> option should not be used with 
+container-managed EntityManagers.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">transaction</code>: A connection is obtained when each transaction
+begins (optimistic or datastore), and is released when the transaction
+completes. Non-transactional connections are obtained on-demand.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">on-demand</code>: Connections are obtained only when needed. This
+option is equivalent to the <code class="literal">transaction</code> option when datastore
+transactions are used. For optimistic transactions, though, it means that a
+connection will be retained only for the duration of the datastore flush and
+commit process.
+                </p>
+            </li></ul></div>
+        <p>
+You can also specify the connection retain mode of individual <code class="classname">
+EntityManager</code>s when you retrieve them from the <code class="classname">
+EntityManagerFactory</code>. See
+<a class="xref" href="ref_guide_runtime_jpa.html#ref_guide_runtime_emfactory" title="2.1.&nbsp; OpenJPAEntityManagerFactory">Section&nbsp;2.1, &#8220;
+                OpenJPAEntityManagerFactory
+            &#8221;</a> for details.
+        </p>
+        <p>
+        <a class="indexterm" name="d5e11507"></a>
+The <a class="link" href="ref_guide_conf_openjpa.html#openjpa.FlushBeforeQueries" title="5.36.&nbsp; openjpa.FlushBeforeQueries"><code class="literal">
+openjpa.FlushBeforeQueries</code></a> configuration property controls
+another aspect of connection usage: whether to flush transactional changes
+before executing object queries. This setting only applies to queries that would
+otherwise have to be executed in-memory because the
+<a class="link" href="ref_guide_conf_openjpa.html#openjpa.IgnoreChanges" title="5.37.&nbsp; openjpa.IgnoreChanges"><code class="literal">IgnoreChanges</code></a>
+property is set to false and the query may involve objects that have been
+changed in the current transaction. Legal values are:
+        </p>
+        <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+                <p>
+<code class="literal">true</code>: Always flush rather than executing the query
+in-memory. If the current transaction is optimistic, OpenJPA will begin a
+non-locking datastore transaction. This is the default.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">false</code>: Never flush before a query.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">with-connection</code>: Flush only if the <code class="classname">EntityManager
+</code> has already established a dedicated connection to the datastore,
+otherwise execute the query in-memory.
+This option is useful if you use long-running optimistic transactions and want
+to ensure that these transactions do not consume database resources until
+commit. OpenJPA's behavior with this option is dependent on the transaction
+status and mode, as well as the configured connection retain mode described
+earlier in this section.
+                </p>
+            </li></ul></div>
+        <p>
+The flush mode can also be varied at runtime using the OpenJPA fetch
+configuration API, discussed in <a class="xref" href="ref_guide_runtime.html" title="Chapter&nbsp;9.&nbsp; Runtime Extensions">Chapter&nbsp;9, <i>
+        Runtime Extensions
+    </i></a>.
+        </p>
+        <p>
+        <a class="indexterm" name="d5e11527"></a>
+The table below describes the behavior of automatic flushing in various
+situations. In all cases, flushing will only occur if OpenJPA detects that you
+have made modifications in the current transaction that may affect the query's
+results.
+        </p>
+        <div class="table"><a name="d5e11530"></a><p class="title"><b>Table&nbsp;4.2.&nbsp;
+                OpenJPA Automatic Flush Behavior
+            </b></p><div class="table-contents">
+            
+            <table summary="&#xA;                OpenJPA Automatic Flush Behavior&#xA;            " border="1"><colgroup><col align="left" class="col1"><col align="left" class="col2"><col align="left" class="col3"><col align="left" class="col4"><col align="left" class="col5"></colgroup><thead><tr><th align="left">
+                        </th><th align="left">
+FlushBeforeQueries = false
+                        </th><th align="left">
+FlushBeforeQueries = true
+                        </th><th align="left">
+FlushBeforeQueries = with-connection; 
+ConnectionRetainMode = on-demand
+                        </th><th align="left">
+FlushBeforeQueries = with-connection; 
+ConnectionRetainMode = transaction or always
+                        </th></tr></thead><tbody><tr><td align="left">
+                            <span class="bold"><strong>
+IgnoreChanges = true
+                            </strong></span>
+                        </td><td align="left">
+no flush
+                        </td><td align="left">
+no flush
+                        </td><td align="left">
+no flush
+                        </td><td align="left">
+no flush
+                        </td></tr><tr><td align="left">
+                            <span class="bold"><strong>
+IgnoreChanges = false; no tx active
+                            </strong></span>
+                        </td><td align="left">
+no flush
+                        </td><td align="left">
+no flush
+                        </td><td align="left">
+no flush
+                        </td><td align="left">
+no flush
+                        </td></tr><tr><td align="left">
+                            <span class="bold"><strong>
+IgnoreChanges = false; datastore tx active
+                            </strong></span>
+                        </td><td align="left">
+no flush
+                        </td><td align="left">
+flush
+                        </td><td align="left">
+flush
+                        </td><td align="left">
+flush
+                        </td></tr><tr><td align="left">
+                            <span class="bold"><strong>
+IgnoreChanges = false; optimistic tx active
+                            </strong></span>
+                        </td><td align="left">
+no flush
+                        </td><td align="left">
+flush
+                        </td><td align="left">
+no flush unless <code class="methodname">flush</code> has already been invoked
+                        </td><td align="left">
+flush
+                        </td></tr></tbody></table>
+        </div></div><br class="table-break">
+        <div class="example"><a name="ref_guide_dbsetup_sql92_retain_conf"></a><p class="title"><b>Example&nbsp;4.11.&nbsp;
+                Specifying Connection Usage Defaults
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+&lt;property name="openjpa.ConnectionRetainMode" value="on-demand"/&gt;
+&lt;property name="openjpa.FlushBeforeQueries" value="true"/&gt;
+</pre>
+        </div></div><br class="example-break">
+        <div class="example"><a name="ref_guide_dbsetup_sql92_retain_runtime"></a><p class="title"><b>Example&nbsp;4.12.&nbsp;
+                Specifying Connection Usage at Runtime
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+import org.apache.openjpa.persistence.*;
+
+// obtaining an em with a certain connection retain mode
+Map props = new HashMap();
+props.put("openjpa.ConnectionRetainMode", "always");
+EntityManager em = emf.createEntityManager(props);
+</pre>
+        </div></div><br class="example-break">
+    </div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_dbsetup_multidb.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide_dbsetup.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_stmtbatch.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">7.&nbsp;
+            Accessing Multiple Databases
+        &nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;9.&nbsp;
+            Statement Batching
+        </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_retain.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_sql92.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_sql92.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_sql92.html Wed May 14 22:22:23 2014
@@ -0,0 +1,78 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>6.&nbsp; Setting the SQL Join Syntax</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide_dbsetup.html" title="Chapter&nbsp;4.&nbsp; JDBC"><link rel="prev" href="ref_guide_dbsetup_isolation.html" title="5.&nbsp; Setting the Transaction Isolation"><link rel="next" href="ref_guide_dbsetup_multidb.html" title="7.&nbsp; Accessing Multiple Databases"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.&nbsp;
+            Setting the SQL Join Syntax
+        </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_dbsetup_isolation.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;4.&nbsp;
+        JDBC
+    </th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_multidb.html">Next</a></td></tr></table><hr></div><div class="section" title="6.&nbsp; Setting the SQL Join Syntax"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="ref_guide_dbsetup_sql92">6.&nbsp;
+            Setting the SQL Join Syntax
+        </h2></div></div></div>
+        
+        <a class="indexterm" name="d5e11436"></a>
+        <a class="indexterm" name="d5e11439"></a>
+        <p>
+Object queries often involve using SQL joins behind the scenes. You can
+configure OpenJPA to use either SQL 92-style join syntax, in which joins are
+placed in the SQL FROM clause, the traditional join syntax, in which join
+criteria are part of the WHERE clause, or a database-specific join syntax
+mandated by the <a class="link" href="ref_guide_dbsetup_dbsupport.html#ref_guide_dbsetup_dbdict" title="Example&nbsp;4.7.&nbsp; Specifying a DBDictionary"><code class="classname">
+DBDictionary</code></a>. OpenJPA only supports outer joins when using
+SQL 92 syntax or a database-specific syntax with outer join support.
+        </p>
+        <p>
+The <a class="link" href="ref_guide_conf_jdbc.html#openjpa.jdbc.DBDictionary" title="6.2.&nbsp; openjpa.jdbc.DBDictionary"><code class="literal">
+openjpa.jdbc.DBDictionary</code></a> plugin accepts the <code class="literal">
+JoinSyntax</code> property to set the system's default syntax. The available
+values are:
+        </p>
+        <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+                <p>
+<code class="literal">traditional</code>: Traditional SQL join syntax; outer joins are
+not supported.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">database</code>: The database's native join syntax. Databases that
+do not have a native syntax will default to one of the other options.
+                </p>
+            </li><li class="listitem">
+                <p>
+<code class="literal">sql92</code>: ANSI SQL92 join syntax. Outer joins are supported.
+Not all databases support this syntax.
+                </p>
+            </li></ul></div>
+        <p>
+You can change the join syntax at runtime through the OpenJPA fetch
+configuration API, which is described in <a class="xref" href="ref_guide_runtime.html" title="Chapter&nbsp;9.&nbsp; Runtime Extensions">Chapter&nbsp;9, <i>
+        Runtime Extensions
+    </i></a>.
+        </p>
+        <div class="example"><a name="ref_guide_dbsetup_sql92_conf"></a><p class="title"><b>Example&nbsp;4.9.&nbsp;
+                Specifying the Join Syntax Default
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+&lt;property name="openjpa.jdbc.DBDictionary" value="JoinSyntax=sql92"/&gt;
+</pre>
+        </div></div><br class="example-break">
+        <div class="example"><a name="ref_guide_dbsetup_sql92_fetch"></a><p class="title"><b>Example&nbsp;4.10.&nbsp;
+                Specifying the Join Syntax at Runtime
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+import org.apache.openjpa.persistence.jdbc.*; 
+
+... 
+
+Query q = em.createQuery("select m from Magazine m where m.title = 'JDJ'");
+OpenJPAQuery kq = OpenJPAPersistence.cast(q);
+JDBCFetchPlan fetch = (JDBCFetchPlan) kq.getFetchPlan();
+fetch.setJoinSyntax(JoinSyntax.SQL92);
+List results = q.getResultList();
+</pre>
+        </div></div><br class="example-break">
+    </div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_dbsetup_isolation.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide_dbsetup.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_multidb.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.&nbsp;
+            Setting the Transaction Isolation
+        &nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;7.&nbsp;
+            Accessing Multiple Databases
+        </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_sql92.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_sqlconn.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_sqlconn.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_sqlconn.html Wed May 14 22:22:23 2014
@@ -0,0 +1,82 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>3.&nbsp; Runtime Access to DataSource</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide_dbsetup.html" title="Chapter&nbsp;4.&nbsp; JDBC"><link rel="prev" href="ref_guide_dbsetup_thirdparty.html" title="2.&nbsp; Using a Third-Party DataSource"><link rel="next" href="ref_guide_dbsetup_dbsupport.html" title="4.&nbsp; Database Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.&nbsp;
+            Runtime Access to DataSource
+        </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_dbsetup_thirdparty.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;4.&nbsp;
+        JDBC
+    </th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_dbsupport.html">Next</a></td></tr></table><hr></div><div class="section" title="3.&nbsp; Runtime Access to DataSource"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="ref_guide_dbsetup_sqlconn">3.&nbsp;
+            Runtime Access to DataSource
+        </h2></div></div></div>
+        
+        <a class="indexterm" name="d5e9705"></a>
+        <a class="indexterm" name="d5e9708"></a>
+        <p>
+The JPA standard defines how to access JDBC connections from enterprise beans.
+OpenJPA also provides APIs to retrieve a connection directly from the <code class="classname">
+EntityManagerFactory</code>'s <code class="classname">DataSource</code>.
+        </p>
+        <p>
+The <code class="methodname">EntityManager.unwrap(java.sql.Connection.class)</code> method
+returns an <code class="classname">EntityManager</code>'s connection. If the <code class="classname">
+EntityManager</code> does not already have a connection, it will obtain
+one. The returned connection is only guaranteed to be transactionally consistent
+with other <code class="classname">EntityManager</code> operations if the <code class="classname">
+EntityManager</code> is in a managed or non-optimistic transaction, if the
+<code class="classname">EntityManager</code> has flushed in the current transaction, or
+if you have used the <code class="methodname">OpenJPAEntityManager.beginStore</code>
+method to ensure that a datastore transaction is in progress. Always close the
+returned connection before attempting any other <code class="classname">EntityManager
+</code> operations. OpenJPA will ensure that the underlying native
+connection is not released if a datastore transaction is in progress.
+        </p>
+        <div class="example"><a name="ref_guide_dbsetup_conn_jpa"></a><p class="title"><b>Example&nbsp;4.5.&nbsp;
+                Using the EntityManager's Connection
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+import java.sql.Connection;
+import javax.persistence.EntityManager;
+import javax.persistence.EntityManagerFactory;
+
+...
+
+EntityManager em = emf.createEntityManager();
+Connection conn = (Connection) em.unwrap(java.sql.Connection.class);
+
+// do JDBC stuff
+
+conn.close();
+</pre>
+        </div></div><br class="example-break">
+        <p>
+The example below shows how to use a connection directly from the <code class="classname">
+DataSource</code>, rather than using an <code class="classname"> EntityManager
+</code>'s connection.
+        </p>
+        <div class="example"><a name="ref_guide_dbsetup_conn_from_factory_jpa"></a><p class="title"><b>Example&nbsp;4.6.&nbsp;
+                Using the EntityManagerFactory's DataSource
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+import java.sql.*;
+import javax.sql.*;
+import org.apache.openjpa.conf.*;
+import org.apache.openjpa.persistence.*;
+
+...
+
+OpenJPAEntityManagerFactory kemf = OpenJPAPersistence.cast(emf);
+OpenJPAConfiguration conf = kemf.getConfiguration();
+DataSource dataSource = (DataSource) conf.getConnectionFactory();
+Connection conn = dataSource.getConnection();
+
+// do JDBC stuff
+
+conn.close();
+</pre>
+        </div></div><br class="example-break">
+    </div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_dbsetup_thirdparty.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide_dbsetup.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_dbsupport.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.&nbsp;
+            Using a Third-Party DataSource
+        &nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;4.&nbsp;
+            Database Support
+        </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_sqlconn.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_stmtbatch.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_stmtbatch.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_stmtbatch.html Wed May 14 22:22:23 2014
@@ -0,0 +1,103 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>9.&nbsp; Statement Batching</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide_dbsetup.html" title="Chapter&nbsp;4.&nbsp; JDBC"><link rel="prev" href="ref_guide_dbsetup_retain.html" title="8.&nbsp; Configuring the Use of JDBC Connections"><link rel="next" href="ref_guide_dbsetup_lrs.html" title="10.&nbsp; Large Result Sets"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">9.&nbsp;
+            Statement Batching
+        </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_dbsetup_retain.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;4.&nbsp;
+        JDBC
+    </th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_lrs.html">Next</a></td></tr></table><hr></div><div class="section" title="9.&nbsp; Statement Batching"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="ref_guide_dbsetup_stmtbatch">9.&nbsp;
+            Statement Batching
+        </h2></div></div></div>
+        
+        <a class="indexterm" name="d5e11583"></a>
+        <a class="indexterm" name="d5e11585"></a>
+        <p>
+In addition to connection pooling and prepared statement caching, OpenJPA 
+employs statement batching to speed up JDBC updates. Statement batching is 
+enabled by default for any JDBC driver that supports it. When batching is on, 
+OpenJPA automatically orders its SQL statements to maximize the size of each 
+batch. This can result in large performance gains for transactions that modify 
+a lot of data.
+		</p>
+		<p>
+You configure statement batching through the system DBDictionary, which is 
+controlled by the openjpa.jdbc.DBDictionary configuration property. You can 
+enable the statement batching by setting the batchLimit in the value. The batch
+limit is the maximum number of statements OpenJPA will ever batch 
+together. A value has the following meaning:
+			</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+               	 <p>
+<code class="literal">-1</code>: Unlimited number of statements for a batch. 
+                </p>
+               </li><li class="listitem">
+                <p>
+<code class="literal">0</code>: Disable batch support. This is the default for most 
+dictionaries.
+                </p>
+               </li><li class="listitem">
+                <p>
+<code class="literal">any positive number</code>: Maximum number of statements for a batch.
+                </p>
+               </li></ul></div><p> 
+			</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
+		     <p>
+By default, the batch support is based on each Dictionary to define the default 
+batch limit. Currently only DB2 and Oracle dictionaries are set the default 
+batch limit to 100. The default batch limit for the rest of the dictionaries is set 
+to zero (disabled). 
+			</p>
+			</div><p>
+		</p>
+		<p>
+The example below shows how to enable and disable statement batching via 
+your configuration properties. 
+        </p>
+        <div class="example"><a name="ref_guide_dbsetup_stmtbatch_exmple1"></a><p class="title"><b>Example&nbsp;4.13.&nbsp;
+                Enable SQL statement batching
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+&lt;property name="openjpa.jdbc.DBDictionary" value="db2(batchLimit=25)"/&gt;
+&lt;property name="openjpa.jdbc.DBDictionary" value="oracle(batchLimit=-1)"/&gt;
+Or
+&lt;property name="openjpa.jdbc.DBDictionary" value="batchLimit=25"/&gt;
+&lt;property name="openjpa.jdbc.DBDictionary" value="batchLimit=-1"/&gt;
+</pre>
+        </div></div><br class="example-break">
+        <div class="example"><a name="ref_guide_dbsetup_stmtbatch_exmple2"></a><p class="title"><b>Example&nbsp;4.14.&nbsp;
+                Disable SQL statement batching
+            </b></p><div class="example-contents">
+                        
+<pre class="programlisting">
+&lt;property name="openjpa.jdbc.DBDictionary" value="db2(batchLimit=0)"/&gt;
+Or
+&lt;property name="openjpa.jdbc.DBDictionary" value="batchLimit=0"/&gt;
+</pre>
+        </div></div><br class="example-break">
+        <p>
+By default, org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager 
+is the default statement batching implementation. OPENJPA also 
+provides another update manager 
+org.apache.openjpa.jdbc.kernel.BatchingOperationOrderUpdateManager for the
+statements that required ordering.  You can plug-in this update manager through
+the "openjpa.jdbc.UpdateManager" property. Or you can plug-in your own
+statement batching implementation by providing the implementation that extends 
+from AbstractUpdateManager, ConstraitUpdateManager or OperationOrderUpdateManager. 
+Add this implementation
+class as a property in the persistence.xml file. For example, a custom
+statement batching implementation mycomp.MyUpdateManager extends 
+ConstraitUpdateManager. You specify this implementation in the persistence.xml
+file as the following example:
+        </p>
+         <div class="example"><a name="ref_guide_dbsetup_stmtbatch_exmple3"></a><p class="title"><b>Example&nbsp;4.15.&nbsp;
+                Plug-in custom statement batching implementation
+            </b></p><div class="example-contents">
+                        
+<pre class="programlisting">
+&lt;property name="openjpa.jdbc.UpdateManager" value="mycomp.MyUpdateManager"/&gt;
+</pre>
+        </div></div><br class="example-break">        
+    </div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_dbsetup_retain.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide_dbsetup.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_lrs.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">8.&nbsp;
+            Configuring the Use of JDBC Connections
+        &nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;10.&nbsp;
+            Large Result Sets
+        </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_stmtbatch.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_thirdparty.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_thirdparty.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_thirdparty.html Wed May 14 22:22:23 2014
@@ -0,0 +1,237 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>2.&nbsp; Using a Third-Party DataSource</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide_dbsetup.html" title="Chapter&nbsp;4.&nbsp; JDBC"><link rel="prev" href="ref_guide_dbsetup.html" title="Chapter&nbsp;4.&nbsp; JDBC"><link rel="next" href="ref_guide_dbsetup_sqlconn.html" title="3.&nbsp; Runtime Access to DataSource"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.&nbsp;
+            Using a Third-Party DataSource
+        </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_dbsetup.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;4.&nbsp;
+        JDBC
+    </th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_sqlconn.html">Next</a></td></tr></table><hr></div><div class="section" title="2.&nbsp; Using a Third-Party DataSource"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="ref_guide_dbsetup_thirdparty">2.&nbsp;
+            Using a Third-Party DataSource
+        </h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_thirdparty_enlist">2.1. 
+                Managed and XA DataSources
+            </a></span></dt><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSatRuntime">2.2. Setting the DataSource at runtime</a></span></dt><dd><dl><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSPerEM">2.2.1. Using different DataSources for each EntityManager</a></span></dt><dd><dl><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSBenefits">2.2.1.1. Benefits</a></span></dt><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSLimitations">2.2.1.2. Limitations</a></span></dt><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSError">2.2.1.3. Error handling</a></span></dt></dl></dd></dl></dd></dl></div>
+        
+        <a class="indexterm" name="d5e9568"></a>
+        <p>
+You can use OpenJPA with any third-party <code class="classname">javax.sql.DataSource
+</code>. There are multiple ways of telling OpenJPA about a <code class="classname">
+DataSource</code>:
+        </p>
+        <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+                <p>
+                <a class="indexterm" name="d5e9577"></a>
+Set the <code class="classname">DataSource</code> into the map passed to <code class="methodname">
+Persistence.createEntityManagerFactory</code> under the
+<a class="link" href="ref_guide_conf_openjpa.html#openjpa.ConnectionFactory" title="5.10.&nbsp; openjpa.ConnectionFactory"><code class="literal">openjpa.ConnectionFactory
+</code></a> key.
+                </p>
+            </li><li class="listitem">
+                <p>
+                <a class="indexterm" name="d5e9585"></a>
+Bind the <code class="classname">DataSource</code> into JNDI, and then specify its
+location in the <code class="literal">jta-data-source</code> or 
+<code class="literal">non-jta-data-source</code> element of the
+<a class="link" href="jpa_overview_persistence.html#jpa_overview_persistence_xml" title="1.&nbsp; persistence.xml">JPA XML format</a> (depending on
+whether the <code class="classname">DataSource</code> is managed by JTA), or in the
+<a class="link" href="ref_guide_conf_openjpa.html#openjpa.ConnectionFactoryName" title="5.12.&nbsp; openjpa.ConnectionFactoryName">
+<code class="literal">openjpa.ConnectionFactoryName</code></a> property.
+                </p>
+            </li><li class="listitem">
+                <p>
+                <a class="indexterm" name="d5e9596"></a>
+Specify the full class name of the <code class="classname">DataSource</code>
+implementation in the <a class="link" href="ref_guide_conf_openjpa.html#openjpa.ConnectionDriverName" title="5.8.&nbsp; openjpa.ConnectionDriverName">
+<code class="literal">openjpa.ConnectionDriverName</code></a> property in place of a JDBC
+driver. In this configuration OpenJPA will instantiate an instance of the named
+class via reflection. It will then configure the <code class="classname">DataSource
+</code> with the properties in the
+<a class="link" href="ref_guide_conf_openjpa.html#openjpa.ConnectionProperties" title="5.19.&nbsp; openjpa.ConnectionProperties">
+<code class="literal">openjpa.ConnectionProperties</code></a> setting.
+                </p>
+            </li></ul></div>
+        <p>
+The features of OpenJPA's own <code class="classname">DataSource</code> can
+also be used with third-party implementations. OpenJPA layers on top of the
+third-party <code class="classname">DataSource</code> to provide the extra
+functionality. To configure these features use the 
+<a class="link" href="ref_guide_conf_openjpa.html#openjpa.ConnectionFactoryProperties" title="5.15.&nbsp; openjpa.ConnectionFactoryProperties">
+<code class="literal">openjpa.ConnectionFactoryProperties</code></a> property described
+in the previous section.
+        </p>
+        <div class="example"><a name="ref_guide_dbsetup_thirdparty_ex"></a><p class="title"><b>Example&nbsp;4.2.&nbsp;
+                Properties File for a Third-Party DataSource
+            </b></p><div class="example-contents">
+            
+<pre class="programlisting">
+&lt;property name="openjpa.ConnectionDriverName" value="oracle.jdbc.pool.OracleDataSource"/&gt;
+&lt;property name="openjpa.ConnectionProperties" 
+    value="PortNumber=1521, ServerName=saturn, DatabaseName=solarsid, DriverType=thin"/&gt;
+&lt;property name="openjpa.ConnectionFactoryProperties" value="QueryTimeout=5000"/&gt;
+</pre>
+            <p>
+You can also force the Apache Commons DBCP BasicDataSource to be used for
+connection pooling when provided on the classpath by substituting it as the
+<code class="literal">ConnectionDriverName</code> and setting 
+<code class="literal">ConnectionProperties=DriverClassName</code> to the actual JDBC
+driver value -
+            </p>
+<pre class="programlisting">
+&lt;property name="openjpa.ConnectionDriverName" value="org.apache.commons.dbcp.BasicDataSource"/&gt;
+&lt;property name="openjpa.ConnectionProperties" 
+    value="DriverClassName=oracle.jdbc.pool.OracleDataSource, PortNumber=1521, ServerName=saturn, DatabaseName=solarsid, DriverType=thin, MaxIdle=0"/&gt;
+&lt;property name="openjpa.ConnectionFactoryProperties" value="QueryTimeout=5000"/&gt;
+</pre>
+        </div></div><br class="example-break">
+        <div class="section" title="2.1.&nbsp; Managed and XA DataSources"><div class="titlepage"><div><div><h3 class="title" id="ref_guide_dbsetup_thirdparty_enlist">2.1.&nbsp;
+                Managed and XA DataSources
+            </h3></div></div></div>
+            
+            <a class="indexterm" name="d5e9618"></a>
+            <a class="indexterm" name="d5e9621"></a>
+            <p>
+            <a class="indexterm" name="d5e9625"></a>
+Certain application servers automatically enlist their <code class="classname"> DataSource
+</code>s in global transactions. When this is the case, OpenJPA should not
+attempt to commit the underlying connection, leaving JDBC transaction completion
+to the application server. To notify OpenJPA that your third-party <code class="classname">
+DataSource</code> is managed by the application server, use the 
+<code class="literal">jta-data-source</code> element of your <code class="filename">
+persistence.xml</code> file or set the
+<a class="link" href="ref_guide_conf_openjpa.html#openjpa.ConnectionFactoryMode" title="5.14.&nbsp; openjpa.ConnectionFactoryMode">
+<code class="literal">openjpa.ConnectionFactoryMode</code></a> property to 
+<code class="literal">managed</code>.
+            </p>
+            <p>
+Note that OpenJPA can only use managed <code class="classname">DataSource</code>s when
+it is also integrating with the application server's managed transactions. Also
+note that all XA <code class="classname">DataSource</code>s are enlisted, and you must
+set this property when using any XA <code class="classname"> DataSource</code>.
+            </p>
+            <p>
+When using a managed <code class="classname">DataSource</code>, you should also
+configure a second unmanaged <code class="classname">DataSource</code> that OpenJPA can
+use to perform tasks that are independent of the global transaction. The most
+common of these tasks is updating the sequence table OpenJPA uses to generate
+unique primary key values for your datastore identity objects. Configure the
+second <code class="classname">DataSource</code> using the <code class="literal">non-jta-data-source
+</code> <code class="filename">persistence.xml</code> element, or OpenJPA's various
+"2" connection properties, such as <code class="literal">openjpa.ConnectionFactory2Name
+</code> or <code class="literal">openjpa.Connection2DriverName</code>. These
+properties are outlined in <a class="xref" href="ref_guide_conf.html" title="Chapter&nbsp;2.&nbsp; Configuration">Chapter&nbsp;2, <i>
+        Configuration
+    </i></a>.
+            </p>
+            <div class="example"><a name="ref_guide_enterprise_xa_conf_ex"></a><p class="title"><b>Example&nbsp;4.3.&nbsp;
+                    Managed DataSource Configuration
+                </b></p><div class="example-contents">
+                
+<pre class="programlisting">
+&lt;!-- managed DataSource --&gt;
+&lt;jta-data-source&gt;java:/OracleXASource&lt;/jta-data-source&gt;
+&lt;properties&gt;
+    &lt;!-- use OpenJPA's built-in DataSource for unmanaged connections --&gt;
+    &lt;property name="openjpa.Connection2UserName" value="scott"/&gt;
+    &lt;property name="openjpa.Connection2Password" value="tiger"/&gt;
+    &lt;property name="openjpa.Connection2URL" value="jdbc:oracle:thin:@CROM:1521:OpenJPADB"/&gt;
+    &lt;property name="openjpa.Connection2DriverName" value="oracle.jdbc.driver.OracleDriver"/&gt;
+&lt;/properties&gt;
+</pre>
+            </div></div><br class="example-break">
+        </div>
+        <div class="section" title="2.2.&nbsp;Setting the DataSource at runtime"><div class="titlepage"><div><div><h3 class="title" id="ref_guide_dbsetup_setDSatRuntime">2.2.&nbsp;Setting the DataSource at runtime</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSPerEM">2.2.1. Using different DataSources for each EntityManager</a></span></dt><dd><dl><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSBenefits">2.2.1.1. Benefits</a></span></dt><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSLimitations">2.2.1.2. Limitations</a></span></dt><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSError">2.2.1.3. Error handling</a></span></dt></dl></dd></dl></div>
+            
+            <a class="indexterm" name="d5e9652"></a>
+            <p> 
+As mentioned above, the JTA and Non-JTA DataSources may be passed in as configuration properties
+at EntityManagerFactory creation. Either the JPA standard properties (
+<code class="literal">javax.persistence.jtaDataSource</code>, <code class="literal">java.persistence.nonJtaDataSource</code>) 
+or their OpenJPA specific equivalents (<code class="literal">openjpa.ConnectionFactoryName</code>, 
+<code class="literal">openjpa.ConnectionFactory2Name</code>) may be used. One use case for this function is to 
+store production connection information in configuration files but override the value when testing. 
+            </p>
+            <p>
+            </p><div class="example"><a name="d5e9661"></a><p class="title"><b>Example&nbsp;4.4.&nbsp;
+                    Setting DataSource at Runtime
+                </b></p><div class="example-contents">
+                
+                <pre class="programlisting">Map&lt;Object,Object&gt; props = new HashMap&lt;Object,Object&gt;();
+props.put("javax.persistence.jtaDataSource", "jdbc/myDataSource");
+props.put("javax.persistence.nonJtaDataSource", "jdbc/myNonJTADataSource");
+emf = Persistence.createEntityManagerFactory("example", props);</pre>
+            </div></div><p><br class="example-break">
+            </p>
+                <div class="section" title="2.2.1.&nbsp;Using different DataSources for each EntityManager"><div class="titlepage"><div><div><h4 class="title" id="ref_guide_dbsetup_setDSPerEM">2.2.1.&nbsp;Using different DataSources for each EntityManager</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSBenefits">2.2.1.1. Benefits</a></span></dt><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSLimitations">2.2.1.2. Limitations</a></span></dt><dt><span class="section"><a href="ref_guide_dbsetup_thirdparty.html#ref_guide_dbsetup_setDSError">2.2.1.3. Error handling</a></span></dt></dl></div>
+                 
+                <p>
+The JPA specification allows the DataSource (ConnectionFactory) to be specified on the 
+EntityManagerFactory. OpenJPA extends this support and allows each EntityManager to override the 
+DataSource from the EntityManagerFactory. It's expected that the EntityManagerFactory will also be 
+configured with a valid JTA / Non-JTA DataSource. The DataSource configured on the 
+EntityManagerFactory will be used to obtain a DBDictionary and (rarely) to gather some information
+about the database in use (e.g. version, JDBC driver version). 
+                </p>
+                <p>
+                    If the EntityManagerFactory is not configured with a valid DataSource there are
+                    a few additional caveats. 
+                    </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The <code class="literal">openjpa.DBDictionary</code> property must be
+                        used to ensure the correct DBDictionary is used.</p></li><li class="listitem"><p>OpenJPA will always attempt to obtain a DataSource from JNDI
+                        based on the configuration for the EntityManagerFactory. When a JNDI name is
+                        specified on the EntityManager this lookup happens slightly earlier than 
+                        normal. If the lookup fails the JNDI name provided at EntityManager creation
+                        will be set into the EntityManagerFactory's configuration and used in
+                        subsequent attempts. </p></li></ul></div><p>
+                </p>
+                <div class="section" title="2.2.1.1.&nbsp;Benefits"><div class="titlepage"><div><div><h5 class="title" id="ref_guide_dbsetup_setDSBenefits">2.2.1.1.&nbsp;Benefits</h5></div></div></div>
+                    
+                    <p>
+                    In effect this option allows a single set of entity definitions to be shared 
+                    between multiple database instances or schemas within an instance. This can be
+                    highly beneficial when there are a large number of entity definitions (e.g. &gt;
+                    200), or a large number of databases / schemas in use.
+                    </p> 
+                </div>
+                <div class="section" title="2.2.1.2.&nbsp;Limitations"><div class="titlepage"><div><div><h5 class="title" id="ref_guide_dbsetup_setDSLimitations">2.2.1.2.&nbsp;Limitations</h5></div></div></div>
+                    
+                    <p>
+                        </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+                                <p>The same database type and version must be used by each 
+                                EntityManager. OpenJPA will use the same DBDictionary for each
+                                EntityManager and will make no attempt to alter SQL syntax 
+                                between EntityManager instances. 
+                            </p>
+                            </li><li class="listitem"><p>It is the application's responsibility to ensure 
+                            that the schema is identical on each database.</p></li><li class="listitem"><p>The application may not specify schema names for 
+                            individual entities.</p></li><li class="listitem">
+                                <p>The DataSource (ConnectionFactory) name may only be 
+                                specified when the EntityManager is created. The DataSource 
+                                may not be switched while an EntityManager is in use.
+                                </p>
+                            </li><li class="listitem"><p>The L2 cache (DataCache) should not be used if 
+                            different DataSources are specified for each EntityManager</p>
+                            </li><li class="listitem"><p>SynchronizeMappings should not be used with this 
+                            feature.</p></li><li class="listitem"><p>Table and Sequence generators should not be used 
+                            with this feature.</p></li><li class="listitem"><p>It is not required, but is recommended that the 
+                            <code class="literal">openjpa.DBDictionary</code> property be specified when 
+                            using this feature</p></li></ul></div><p>
+                    </p> 
+                </div>
+                <div class="section" title="2.2.1.3.&nbsp;Error handling"><div class="titlepage"><div><div><h5 class="title" id="ref_guide_dbsetup_setDSError">2.2.1.3.&nbsp;Error handling</h5></div></div></div>
+                    
+                    <p>
+                    If a JTA DataSource is not available when the EntityManager is created, an 
+                    <code class="literal">IllegalArgumentException</code> will be thrown.
+                    The EntityManager will not fall back to the JTA DataSource defined in the 
+                    configuration. 
+                    </p> 
+                    <p>
+                    The same logic applies if a Non-JTA DataSource is not available when the 
+                    EntityManager is created. OpenJPA will not fall back to the configured 
+                    Non-JTA DataSource.
+                    </p>
+                </div>
+            </div>
+        </div>
+    </div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_dbsetup.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide_dbsetup.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_dbsetup_sqlconn.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter&nbsp;4.&nbsp;
+        JDBC
+    &nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;3.&nbsp;
+            Runtime Access to DataSource
+        </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_dbsetup_thirdparty.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_deploy.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_deploy.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_deploy.html Wed May 14 22:22:23 2014
@@ -0,0 +1,80 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>Chapter&nbsp;8.&nbsp; Deployment</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide.html" title="Part&nbsp;3.&nbsp;Reference Guide"><link rel="prev" href="ref_guide_orphan.html" title="11.&nbsp; Orphaned Keys"><link rel="next" href="ref_guide_enterprise_trans.html" title="2.&nbsp; Integrating with the Transaction Manager"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter&nbsp;8.&nbsp;
+        Deployment
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_orphan.html">Prev</a>&nbsp;</td><th width="60%" align="center">Part&nbsp;3.&nbsp;Reference Guide</th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_enterprise_trans.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter&nbsp;8.&nbsp; Deployment" id="ref_guide_deploy"><div class="titlepage"><div><div><h2 class="title">Chapter&nbsp;8.&nbsp;
+        Deployment
+    </h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ref_guide_deploy.html#ref_guide_deploy_factory">1. 
+            Factory Deployment
+        </a></span></dt><dd><dl><dt><span class="section"><a href="ref_guide_deploy.html#ref_guide_deploy_factory_standalone">1.1. 
+                Standalone Deployment
+            </a></span></dt><dt><span class="section"><a href="ref_guide_deploy.html#ref_guide_deploy_inject">1.2. 
+                EntityManager Injection
+            </a></span></dt></dl></dd><dt><span class="section"><a href="ref_guide_enterprise_trans.html">2. 
+            Integrating with the Transaction Manager
+        </a></span></dt><dt><span class="section"><a href="ref_guide_enterprise_xa.html">3. 
+            XA Transactions
+        </a></span></dt><dd><dl><dt><span class="section"><a href="ref_guide_enterprise_xa.html#ref_guide_enterprise_xa_req">3.1. 
+                Using OpenJPA with XA Transactions
+            </a></span></dt></dl></dd></dl></div>
+    
+    <p>
+OpenJPA deployment includes choosing a factory deployment strategy, and in a
+managed environment, optionally integrating with your application server's
+managed and XA transactions. This chapter examines each aspect of deployment in
+turn.
+    </p>
+    <div class="section" title="1.&nbsp; Factory Deployment"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="ref_guide_deploy_factory">1.&nbsp;
+            Factory Deployment
+        </h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ref_guide_deploy.html#ref_guide_deploy_factory_standalone">1.1. 
+                Standalone Deployment
+            </a></span></dt><dt><span class="section"><a href="ref_guide_deploy.html#ref_guide_deploy_inject">1.2. 
+                EntityManager Injection
+            </a></span></dt></dl></div>
+        
+        <p>
+OpenJPA offers two <code class="classname">EntityManagerFactory</code>
+deployment options.
+        </p>
+        <div class="section" title="1.1.&nbsp; Standalone Deployment"><div class="titlepage"><div><div><h3 class="title" id="ref_guide_deploy_factory_standalone">1.1.&nbsp;
+                Standalone Deployment
+            </h3></div></div></div>
+            
+            <a class="indexterm" name="d5e15079"></a>
+            <p>
+The JPA Overview describes the <code class="classname">javax.persistence.Persistence
+</code> class. You can use <code class="classname">Persistence</code> to obtain
+<code class="classname">EntityManagerFactory</code> instances, as demonstrated in
+<a class="xref" href="jpa_overview_persistence.html" title="Chapter&nbsp;6.&nbsp; Persistence">Chapter&nbsp;6, <i>
+        Persistence
+    </i></a>. OpenJPA also extends
+<code class="classname">Persistence</code> to add additional <code class="classname">
+EntityManagerFactory</code> creation methods. The <code class="classname">
+org.apache.openjpa.persistence.OpenJPAPersistence</code> class
+<a class="ulink" href="../javadoc/org/apache/openjpa/persistence/OpenJPAPersistence.html" target="_top">
+Javadoc</a> details these extensions.
+            </p>
+            <p>
+After obtaining the factory, you can cache it for all <code class="classname">
+EntityManager</code> creation duties.  OpenJPA factories support being 
+bound to JNDI as well.
+            </p>
+        </div>
+        <div class="section" title="1.2.&nbsp; EntityManager Injection"><div class="titlepage"><div><div><h3 class="title" id="ref_guide_deploy_inject">1.2.&nbsp;
+                EntityManager Injection
+            </h3></div></div></div>
+            
+            <p>
+Java EE application servers allow you to <span class="emphasis"><em>inject</em></span> 
+entity managers into your session beans using the <code class="literal">PersistenceContext
+</code> annotation.  See your application server documentation for details.
+            </p>
+        </div>
+    </div>
+	
+    
+</div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_orphan.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_enterprise_trans.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">11.&nbsp;
+            Orphaned Keys
+        &nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;2.&nbsp;
+            Integrating with the Transaction Manager
+        </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_deploy.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_encryption.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_encryption.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_encryption.html Wed May 14 22:22:23 2014
@@ -0,0 +1,34 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>Chapter&nbsp;11.&nbsp; Encryption Provider</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide.html" title="Part&nbsp;3.&nbsp;Reference Guide"><link rel="prev" href="ref_guide_cache_querysql.html" title="3.&nbsp;Prepared SQL Cache"><link rel="next" href="ref_guide_remote.html" title="Chapter&nbsp;12.&nbsp; Remote and Offline Operation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter&nbsp;11.&nbsp;
+        Encryption Provider
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_cache_querysql.html">Prev</a>&nbsp;</td><th width="60%" align="center">Part&nbsp;3.&nbsp;Reference Guide</th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_remote.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter&nbsp;11.&nbsp; Encryption Provider" id="ref_guide_encryption"><div class="titlepage"><div><div><h2 class="title">Chapter&nbsp;11.&nbsp;
+        Encryption Provider
+    </h2></div></div></div>
+    
+    <p>
+	OpenJPA provides an interface for a provider to implement 
+	connection password encryption. Whenever a connection password 
+	is needed, the <code class="methodname">decrypt(String)</code> method will be invoked. See 
+	<a class="ulink" href="../javadoc/org/apache/openjpa/lib/encryption/EncryptionProvider.html" target="_top">
+	<code class="classname">org.apache.openjpa.lib.encryption.EncryptionProvider</code>
+	</a> for the detailed Javadoc. 
+    </p>
+    <p>
+    	Notes:
+    </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+            <p>
+                It is an OpenJPA user responsibility to implement the
+                <code class="classname">EncryptionProvider</code>
+                interface. There is no default implementation.
+            </p>
+        </li><li class="listitem">
+            <p>
+                The interface has an <code class="methodname">encrypt(String)</code> method,
+                but it is not called by the OpenJPA runtime. 
+            </p>
+        </li></ul></div><p>        
+    </p>
+</div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_cache_querysql.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_remote.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.&nbsp;Prepared SQL Cache&nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;Chapter&nbsp;12.&nbsp;
+        Remote and Offline Operation
+    </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_encryption.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_enterprise_abstractstore.html
==============================================================================
--- websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_enterprise_abstractstore.html (added)
+++ websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_enterprise_abstractstore.html Wed May 14 22:22:23 2014
@@ -0,0 +1,25 @@
+<html><head>
+      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+   <title>8.&nbsp; Non-Relational Stores</title><base href="display"><link rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up" href="ref_guide_runtime.html" title="Chapter&nbsp;9.&nbsp; Runtime Extensions"><link rel="prev" href="ref_guide_runtime_pm_event.html" title="7.&nbsp; Transaction Events"><link rel="next" href="ref_guide_caching.html" title="Chapter&nbsp;10.&nbsp; Caching"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">8.&nbsp;
+            Non-Relational Stores
+        </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ref_guide_runtime_pm_event.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;9.&nbsp;
+        Runtime Extensions
+    </th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ref_guide_caching.html">Next</a></td></tr></table><hr></div><div class="section" title="8.&nbsp; Non-Relational Stores"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="ref_guide_enterprise_abstractstore">8.&nbsp;
+            Non-Relational Stores
+        </h2></div></div></div>
+        
+        <p>
+It is possible to adapt OpenJPA to access a non-relational datastore by creating
+an implementation of the
+<a class="ulink" href="../javadoc/org/apache/openjpa/kernel/StoreManager.html" target="_top"><code class="literal">
+org.apache.openjpa.kernel.StoreManager</code></a> interface. OpenJPA
+provides an abstract <code class="literal">StoreManager</code> implementation to
+facilitate this process. See the <code class="literal">org.apache.openjpa.abstractstore
+</code> package <a class="ulink" href="../javadoc/org/apache/openjpa/abstractstore/package-summary.html" target="_top">
+Javadoc</a> for details.
+        </p>
+    </div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ref_guide_runtime_pm_event.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ref_guide_runtime.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ref_guide_caching.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">7.&nbsp;
+            Transaction Events
+        &nbsp;</td><td width="20%" align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;Chapter&nbsp;10.&nbsp;
+        Caching
+    </td></tr></table></div></body></html>
\ No newline at end of file

Propchange: websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/ref_guide_enterprise_abstractstore.html
------------------------------------------------------------------------------
    svn:mime-type = text/plain



Mime
View raw message