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/03/28 23:24:30 UTC
svn commit: r1086408 - in /openjpa/trunk/openjpa-project/src/doc/manual:
migration_considerations.xml ref_guide_conf.xml ref_guide_dbsetup.xml
ref_guide_instrumentation.xml ref_guide_optimization.xml
Author: mtylenda
Date: Mon Mar 28 21:24:30 2011
New Revision: 1086408
URL: http://svn.apache.org/viewvc?rev=1086408&view=rev
Log:
OPENJPA-1932: Documentation update: remove non-existing oracle option from savepoint managers, fix typos, improve letter case.
Modified:
openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml
openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_conf.xml
openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_instrumentation.xml
openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_optimization.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=1086408&r1=1086407&r2=1086408&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/migration_considerations.xml Mon Mar 28 21:24:30 2011
@@ -320,7 +320,7 @@
application characteristics, this default QueryCache
enablement actually could negate much of the potential
gains achieved by using the DataCache. Thus, the default
- value for the openjpa.QueryCache property will now by
+ value for the openjpa.QueryCache property is now
<emphasis><literal>false</literal></emphasis>.
</para>
<para>
@@ -383,7 +383,7 @@
</para>
<para>
The requirement for sequence modification applies to all databases that support sequences, regardless of
- the <literal>CACHE</literal> clause being supported. The only excpetion is Firebird database -
+ the <literal>CACHE</literal> clause being supported. The only exception is Firebird database -
since with this database the increment step is determined during sequence
value fetch, no migration activity is needed.
</para>
Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_conf.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_conf.xml?rev=1086408&r1=1086407&r2=1086408&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_conf.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_conf.xml Mon Mar 28 21:24:30 2011
@@ -3186,7 +3186,7 @@ SavepointManager
</para>
<para>
<emphasis role="bold">Possible values: </emphasis><literal>in-mem</literal>,
-<literal>jdbc</literal>, <literal>oracle</literal>
+<literal>jdbc</literal>
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
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=1086408&r1=1086407&r2=1086408&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 Mon Mar 28 21:24:30 2011
@@ -491,12 +491,12 @@ emf = Persistence.createEntityManagerFac
</example>
</para>
<section id="ref_guide_dbsetup_setDSPerEM">
- <title>Using different datasources for each EntityManager</title>
+ <title>Using different DataSources for each EntityManager</title>
<para>
The JPA specification allows the DataSource (ConnectionFactory) to be specified on the
-EntityManagerFactory.OpenJPA extends this support and allows each EntityManager to override 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 / nonJta DataSource. The DataSource configured on the
+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).
</para>
@@ -506,7 +506,7 @@ about the database in use (e.g. version,
<itemizedlist>
<listitem><para>The <literal>openjpa.DBDictionary</literal> property must be
used to ensure the correct DBDictionary is used.</para></listitem>
- <listitem><para>OpenJPA will always attempt to obtain a datasource from JNDI
+ <listitem><para>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
@@ -540,7 +540,7 @@ about the database in use (e.g. version,
individual entities.</para></listitem>
<listitem>
<para>The DataSource (ConnectionFactory) name may only be
- specified when the EntityManager is created. The datasource
+ specified when the EntityManager is created. The DataSource
may not be switched while an EntityManager is in use.
</para>
</listitem>
@@ -568,7 +568,7 @@ about the database in use (e.g. version,
<para>
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.
+ Non-JTA DataSource.
</para>
</section>
</section>
Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_instrumentation.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_instrumentation.xml?rev=1086408&r1=1086407&r2=1086408&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_instrumentation.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_instrumentation.xml Mon Mar 28 21:24:30 2011
@@ -91,7 +91,7 @@
-Dcom.sun.management.jmxremote.port=<port>.
For example:
<programlisting>
- java -cp openjpa-all-2.1.0.jar:myApplication.jar -Dcom.sun.management.jmxremote.authenticate=false
+ java -cp openjpa-all-2.2.0.jar:myApplication.jar -Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=8888 com.my.app.Main
</programlisting>
</para>
Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_optimization.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_optimization.xml?rev=1086408&r1=1086407&r2=1086408&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_optimization.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_optimization.xml Mon Mar 28 21:24:30 2011
@@ -61,7 +61,7 @@ more work onto the server will have a ne
<row>
<entry colname="name">
<emphasis role="bold">
- Use a Connection Pool
+ Use a connection pool
</emphasis>
<para>
<emphasis>performance, scalability</emphasis>
@@ -70,7 +70,7 @@ more work onto the server will have a ne
<entry colname="desc">
OpenJPA's built-in datasource does not perform connection pooling or
prepared statement caching, but it can use Apache Commons DBCP for connection
-pooling if it is provided on the classpath. Checkout the
+pooling if it is provided on the classpath. Check out the
<link linkend="ref_guide_dbsetup_builtin">DriverDataSource</link>
section, which describes how to use and configure Commons DBCP.
Also, you can manually plug in a third-party pooling datasource like