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/19 21:03:54 UTC
svn commit: r1083273 - in /openjpa/trunk/openjpa-project/src/doc/manual:
jpa_overview_mapping.xml manual.xml ref_guide_pc.xml ref_guide_runtime.xml
ref_guide_slice.xml
Author: mtylenda
Date: Sat Mar 19 20:03:53 2011
New Revision: 1083273
URL: http://svn.apache.org/viewvc?rev=1083273&view=rev
Log:
OPENJPA-1932: Documentation update - copyright year and version, wording corrections.
Modified:
openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_mapping.xml
openjpa/trunk/openjpa-project/src/doc/manual/manual.xml
openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml
openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_runtime.xml
openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_slice.xml
Modified: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_mapping.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_mapping.xml?rev=1083273&r1=1083272&r2=1083273&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_mapping.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_mapping.xml Sat Mar 19 20:03:53 2011
@@ -1042,7 +1042,7 @@ the generator name.
</section>
<section id="jpa_overview_mapping_sequence_tablegen">
<title>
- TableGenerator
+ Table Generator
</title>
<indexterm zone="jpa_overview_mapping_sequence_tablegen">
<primary>
Modified: openjpa/trunk/openjpa-project/src/doc/manual/manual.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/manual.xml?rev=1083273&r1=1083272&r2=1083273&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/manual.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/manual.xml Sat Mar 19 20:03:53 2011
@@ -62,9 +62,9 @@
]>
<book id="manual">
<bookinfo>
- <title>Apache OpenJPA 2.1 User's Guide</title>
+ <title>Apache OpenJPA 2.2 User's Guide</title>
<copyright>
- <year>2006-2010</year>
+ <year>2006-2011</year>
<holder>The Apache Software Foundation</holder>
</copyright>
<releaseinfo>Built from OpenJPA version <?eval ${openjpa.version}?> revision <?eval ${buildNumber}?>.</releaseinfo>
Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml?rev=1083273&r1=1083272&r2=1083273&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml Sat Mar 19 20:03:53 2011
@@ -1013,7 +1013,7 @@ using <literal>IDENTITY</literal> genera
Your database must support auto-increment / identity columns, or some equivalent
(see <xref linkend="ref_guide_dbsetup_dbsupport_oracle"/> for how to
configure a combination of triggers and sequences to fake auto-increment support
-in Oracle).
+in Oracle database).
</para>
</listitem>
<listitem>
Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_runtime.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_runtime.xml?rev=1083273&r1=1083272&r2=1083273&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_runtime.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_runtime.xml Sat Mar 19 20:03:53 2011
@@ -1634,7 +1634,7 @@ tool runs. However, you can manually man
<ulink url="../javadoc/org/apache/openjpa/jdbc/kernel/NativeJDBCSeq.html">
<classname>org.apache.openjpa.jdbc.kernel.NativeJDBCSeq</classname></ulink>.
Many databases have a concept of "native sequences" - a built-in mechanism for
-obtaining incrementing numbers. For example, in Oracle, you can create a
+obtaining incrementing numbers. For example, in Oracle database, you can create a
database sequence with a statement like <literal>CREATE SEQUENCE MYSEQUENCE
</literal>. Sequence values can then be atomically obtained and incremented
with the statement <literal>SELECT MYSEQUENCE.NEXTVAL FROM DUAL</literal>.
Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_slice.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_slice.xml?rev=1083273&r1=1083272&r2=1083273&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_slice.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_slice.xml Sat Mar 19 20:03:53 2011
@@ -345,7 +345,7 @@
</para>
<para>
The order of the names is significant when no <classname>openjpa.slice.Master</classname>
- property is not specified. Then the persistence unit is scanned to find
+ property is not specified. The persistence unit is then scanned to find
all configured slice names and they are ordered alphabetically.
</para>
@@ -439,8 +439,8 @@ public interface DistributionPolicy {
cascaded relationships. Hence user-defined policy has to only decide the
database for the root instance that is the explicit argument to
<methodname>EntityManager.persist()</methodname> call.
- Slice will ensure that all other related instances that gets persisted by cascade
- is assigned to the same database slice as that of the root instance.
+ Slice will ensure that all other related instances that get persisted by cascade
+ are assigned to the same database slice as that of the root instance.
However, the user-defined distribution policy must return the
same slice identifier for the instances that are logically related but
not cascaded for persist.
@@ -450,8 +450,8 @@ public interface DistributionPolicy {
<section id="replication_policy">
<title>Implement ReplicationPolicy interface</title>
<para>
- The entities that are annotated with <classname>@Replicated</classname>
- annotation can be stored in multiple slices as identical copies.
+ The entities that are enumerated in <classname>openjpa.slice.ReplicatedTypes</classname>
+ property can be stored in multiple slices as identical copies.
Specify the implementation class of <classname>ReplicationPolicy</classname> in configuration as
<programlisting>
<![CDATA[ <property name="openjpa.slice.ReplicationPolicy" value="com.acme.foo.MyReplicationPolicy"/>]]>
@@ -508,7 +508,7 @@ the JDBC connection URL of a slice.
for persistence instances automatically or from a specific database
sequence. For such primary key value generation strategy where
a database instance is required, Slice uses a designated slice
- referred as <emphasis>master</emphasis> slice.
+ referred to as <emphasis>master</emphasis> slice.
</para>
<para>
The master slice can be specified explicitly via