openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From allee8...@apache.org
Subject svn commit: r708975 - /openjpa/trunk/openjpa-project/src/doc/manual/
Date Wed, 29 Oct 2008 18:36:39 GMT
Author: allee8285
Date: Wed Oct 29 11:36:39 2008
New Revision: 708975

URL: http://svn.apache.org/viewvc?rev=708975&view=rev
Log:
OPENJPA-751 - Commit documentation changes contributed by Milosz Tylenda.

Modified:
    openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_arch.xml
    openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_em.xml
    openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_emfactory.xml
    openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_mapping.xml
    openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_meta.xml
    openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_pc.xml
    openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_persistence.xml
    openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_query.xml
    openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_trans.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_mapping.xml
    openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml
    openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_optimization.xml
    openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml
    openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_remote.xml
    openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_runtime.xml
    openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_slice.xml
    openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml

Modified: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_arch.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_arch.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_arch.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_arch.xml Wed Oct 29 11:36:39
2008
@@ -110,7 +110,7 @@
                 </primary>
             </indexterm>
 <emphasis role="bold"><link linkend="jpa_overview_pc"><classname>Entity
-</classname></link></emphasis>: Entites are persistent objects that represent
+</classname></link></emphasis>: Entities are persistent objects that represent
 datastore records.
             </para>
         </listitem>

Modified: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_em.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_em.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_em.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_em.xml Wed Oct 29 11:36:39 2008
@@ -530,7 +530,7 @@
                 <para>
 <literal>WRITE</literal>: Other transactions cannot concurrently read or write
 the object. When a transaction is committed that holds WRITE locks on any
-entites, those entites will have their version incremented even if the entities
+entities, those entities will have their version incremented even if the entities
 themselves did not change in the transaction.
                 </para>
             </listitem>

Modified: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_emfactory.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_emfactory.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_emfactory.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_emfactory.xml Wed Oct 29 11:36:39
2008
@@ -127,7 +127,7 @@
         <para>
 The two <methodname>createEntityManager</methodname> methods above create a new
 <classname>EntityManager</classname> each time they are invoked. The optional
-<classname>Map</classname> is used to to supply vendor-specific settings. If
you
+<classname>Map</classname> is used to supply vendor-specific settings. If you
 have configured your implementation for JTA transactions and a JTA transaction
 is active, the returned <classname>EntityManager</classname> will be 
 synchronized with that transaction.
@@ -277,7 +277,7 @@
 When the next transaction begins, the <classname>EntityManager</classname> will
 begin a new persistence context, and will again start returning managed
 entities. As you'll see in <xref linkend="jpa_overview_em"/>, you can
-also merge the previously-detached entites back into the new persistence
+also merge the previously-detached entities back into the new persistence
 context.
             </para>
             <example id="jpa_overview_emfactory_perscontext_transex">
@@ -285,7 +285,7 @@
                     Behavior of Transaction Persistence Context
                 </title>
                 <para>
-The following code illustrates the behavior of entites under an <classname>
+The following code illustrates the behavior of entities under an <classname>
 EntityManager</classname> using a transaction persistence context.
                 </para>
 <programlisting>
@@ -339,7 +339,7 @@
                     Behavior of Extended Persistence Context
                 </title>
                 <para>
-The following code illustrates the behavior of entites under an <classname>
+The following code illustrates the behavior of entities under an <classname>
 EntityManager</classname> using an extended persistence context.
                 </para>
 <programlisting>

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=708975&r1=708974&r2=708975&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 Wed Oct 29 11:36:39
2008
@@ -377,7 +377,7 @@
 In XML, unique constraints are represented by nesting <literal>
 unique-constraint</literal> elements within the <literal> table</literal>
 element. Each <literal>unique-constraint</literal> element in turn nests
-<literal>column-name</literal> text elements to enumerate the contraint's
+<literal>column-name</literal> text elements to enumerate the constraint's
 columns.
         </para>
         <example id="jpa_overview_mapping_unq_attrex">
@@ -2349,7 +2349,7 @@
         </itemizedlist>
         <para>
 The corresponding XML element is <literal> discriminator-column</literal>. Its
-attribues mirror the annotation properties above:
+attributes mirror the annotation properties above:
         </para>
         <itemizedlist>
             <listitem>
@@ -4212,7 +4212,7 @@
 tables</link> or <link linkend="jpa_overview_mapping_bidi">bidirectional
 relations</link>. The only additions are the <classname>MapKey</classname>
 annotation and <literal>map-key</literal> element to declare the key field. We
-covered these additions in in <xref linkend="jpa_overview_meta_mapkey"/>.
+covered these additions in <xref linkend="jpa_overview_meta_mapkey"/>.
             </para>
             <mediaobject>
                 <imageobject>

Modified: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_meta.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_meta.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_meta.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_meta.xml Wed Oct 29 11:36:39
2008
@@ -361,7 +361,7 @@
             <note>
                 <para>
 OpenJPA allows a persistent class to be both an entity and an embeddable class.
-Instances of the class will act as entites when persisted explicitly or assigned
+Instances of the class will act as entities when persisted explicitly or assigned
 to non-embedded fields of entities. Instances will act as embedded values when
 assigned to embedded fields of entities.
                 </para>
@@ -1159,7 +1159,7 @@
 With a mix of eager and lazily-loaded fields, you can ensure that commonly-used
 fields load efficiently, and that other state loads transparently when accessed.
 As you will see in <xref linkend="jpa_overview_emfactory_perscontext"/>,
-you can also use eager fetching to ensure that entites have all needed data
+you can also use eager fetching to ensure that entities have all needed data
 loaded before they become <emphasis>detached</emphasis> at the end of a
 persistence context.
                 </para>

Modified: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_pc.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_pc.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_pc.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_pc.xml Wed Oct 29 11:36:39 2008
@@ -709,7 +709,7 @@
 <emphasis>identity field(s)</emphasis>. If two entities of the same type have
 the same identity field values, then the two entities represent the same state
 in the datastore. Each entity's identity field values must be unique among all
-other entites of the same type.
+other entities of the same type.
         </para>
         <para>
 Identity fields must be primitives, primitive wrappers, <classname>
@@ -1112,7 +1112,7 @@
                     <para>
 <classname>PostLoad</classname> is often used to initialize non-persistent
 fields whose values depend on the values of persistent fields, such as a complex
-datastructure.
+data structure.
                     </para>
                 </listitem>
                 <listitem>

Modified: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_persistence.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_persistence.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_persistence.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_persistence.xml Wed Oct 29 11:36:39
2008
@@ -126,7 +126,7 @@
 persistence</literal>, which then contains one or more <literal>
 persistence-unit</literal> definitions. Each persistence unit describes the
 configuration for the entity managers created by the persistence unit's entity
-manager factory. The persistence unit can specify these elements and attribtues.
+manager factory. The persistence unit can specify these elements and attributes.
         </para>
         <itemizedlist>
             <listitem>

Modified: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_query.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_query.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_query.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_query.xml Wed Oct 29 11:36:39
2008
@@ -1585,7 +1585,7 @@
 of the type of the expression used in declaring the variable. For example,
 consider the previous query: <programlisting>SELECT DISTINCT mag FROM Magazine mag
JOIN mag.articles art JOIN art.author auth WHERE auth.firstName = 'John'
 </programlisting> In the <literal>FROM</literal> clause declaration <literal>
-mag.articles</literal><literal>art</literal>, the identification variable
+mag.articles</literal> <literal>art</literal>, the identification variable
 <literal>art</literal> evaluates to any <literal>Article</literal>
value
 directly reachable from <literal>Magazine</literal>. The association-field
 <literal>articles</literal> is a collection of instances of the abstract schema
@@ -2286,7 +2286,7 @@
                 </para>
                 <para>
 This expression tests whether or not the collection designated by the
-collection-valued path expression is empty (i.e, has no elements).
+collection-valued path expression is empty (i.e. has no elements).
                 </para>
                 <para>
 For example, the following query will return all magazines that don't have any

Modified: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_trans.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_trans.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_trans.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_trans.xml Wed Oct 29 11:36:39
2008
@@ -390,7 +390,7 @@
         </para>
         <para>
 Unless you are using an extended persistence context, committing or rolling back
-also ends the persistence context. All managed entites will be detached from the
+also ends the persistence context. All managed entities will be detached from the
 <classname>EntityManager</classname>.
         </para>
 <programlisting>

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=708975&r1=708974&r2=708975&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 Wed Oct 29 11:36:39 2008
@@ -2834,11 +2834,11 @@
             <para>
                 <emphasis role="bold">Description:</emphasis>
                 The RuntimeUnenhancedClasses property controls how OpenJPA 
-                handles classes that have not been enhanced byt the PCEnhancer 
-                tool or automatically by a javaagent. If RuntimeUnenhanced is 
+                handles classes that have not been enhanced by the PCEnhancer 
+                tool or automatically by a javaagent. If RuntimeUnenhancedClasses is 
                 set to <literal>supported</literal> OpenJPA will automatically

                 create subclasses for unenhanced entity classes. If set to 
-                <literal>unsupported</literal>OpenJPA will not create subclasses

+                <literal>unsupported</literal> OpenJPA will not create subclasses

                 for unenhanced entity classes and will throw an exception when 
                 they are detected. If set to <literal>warn</literal> OpenJPA

                 will not create subclasses for unenhanced entity classes 

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=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml Wed Oct 29 11:36:39
2008
@@ -855,7 +855,7 @@
                     </indexterm>
 <literal>BlobBufferSize</literal>: This property establishes the buffer size
in
 the <literal>INSERT/UPDATE</literal> operations with an 
-<literal>java.io.InputStream</literal>This is only used with OpenJPA's
+<literal>java.io.InputStream</literal>. This is only used with OpenJPA's
 <xref linkend="ref_guide_streamsupport"/>. Defaults to 50000.
                     </para>
                 </listitem>
@@ -972,7 +972,7 @@
                     </indexterm>
 <literal>ClobBufferSize</literal>: This property establish the buffer size in

 the <literal>INSERT/UPDATE</literal> operations with a 
-<literal>java.io.Reader</literal>This is only used with OpenJPA's
+<literal>java.io.Reader</literal>. This is only used with OpenJPA's
 <xref linkend="ref_guide_streamsupport"/>. Defaults to 50000.
                     </para>
                 </listitem>
@@ -2884,7 +2884,7 @@
                             ToUpperCaseFunction
                         </secondary>
                     </indexterm>
-<literal>ToUpperCaseFunction</literal>: SQL function call for for converting
a
+<literal>ToUpperCaseFunction</literal>: SQL function call for converting a
 string to upper case. Use the token <literal>{0}</literal> to represent the
 argument.
                     </para>
@@ -3289,7 +3289,7 @@
                     </indexterm>
 <literal>AutoAssignSequenceName</literal>: The global name of the sequence that
 OpenJPA will assume to hold the value of primary key value for rows that use
-auto-increment. If left unset, OpenJPA will use a the sequence named <literal>
+auto-increment. If left unset, OpenJPA will use a sequence named <literal>
 "SEQ_&lt;table name&gt;"</literal>.
                     </para>
                 </listitem>
@@ -3336,7 +3336,7 @@
                         </secondary>
                     </indexterm>
 <literal>MaxEmbeddedClobSize</literal>: Oracle is unable to persist CLOBs using
-the embedded update method when Clobs get over a certain size. The size depends
+the embedded update method when CLOBs get over a certain size. The size depends
 on database configuration, e.g. encoding. This property defines the maximum size
 CLOB to persist with the embedded method. Defaults to 4000 characters.
                     </para>
@@ -3347,7 +3347,7 @@
 executed against unicode capable columns (the <literal>NCHAR</literal>,
 <literal>NVARCHAR</literal>, <literal>NCLOB</literal> Oracle types)
required
 special handling to be able to store unicode values. Setting this property to
-<literal>true</literal> (the default) will cause OpenJPA to attempt to detect
when the column of
+<literal>true</literal> (the default) will cause OpenJPA to attempt to detect
when the column is
 one of these types, and if so, will attempt to correctly configure the statement
 using the <methodname> OraclePreparedStatement.setFormOfUse</methodname>. For
 more details, see the Oracle
@@ -3388,7 +3388,7 @@
                         </secondary>
                     </indexterm>
 <literal>IgnoreNumericTruncation</literal>: If true, Sybase will ignore numeric
-truncation on SQL operations.  Otherwise, if numeric trunctation is detected, 
+truncation on SQL operations.  Otherwise, if numeric truncation is detected, 
 the operation will fail.
                     </para>
                 </listitem>
@@ -4055,7 +4055,7 @@
                 </indexterm>
 <link linkend="openjpa.jdbc.FetchDirection"><literal>
 openjpa.jdbc.FetchDirection</literal></link>: The expected order in which you
-will access the query results. This property affects the type of datastructure
+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
@@ -4383,7 +4383,7 @@
             <para>
 You can switch freely between schema factories at any time. The XML file format
 used by some factories is detailed in <xref linkend="ref_guide_schema_xml"/>
-. As with any OpenJPA plugin, you can can also implement your own schema
+. As with any OpenJPA plugin, you can also implement your own schema
 factory if you have needs not met by the existing options.
             </para>
         </section>

Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_mapping.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_mapping.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_mapping.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_mapping.xml Wed Oct 29 11:36:39
2008
@@ -547,7 +547,8 @@
                     </listitem>
                     <listitem>
                         <para>
-<literal>-annotations/-ann &lt;true/t | false/f&gt;</literal>: Set to
true to
+<literal>-annotations/-ann &lt;true/t | false/f&gt;</literal>: Set to
+<literal>true</literal> to
 generate JPA annotations in generated java classes.
                         </para>
                     </listitem>
@@ -625,7 +626,7 @@
                         <para>
 <literal>-useBuiltinIdentityClass/-bic &lt;true/t | false/f&gt;</literal>:
Set
 to <literal>false</literal> to prevent the tool from using built-in application
-identity classes when possible. This will force the tool to to create custom
+identity classes when possible. This will force the tool to create custom
 application identity classes even when there is only one primary key column.
                         </para>
                     </listitem>
@@ -732,7 +733,7 @@
             </title>
             <para>
 The <classname>org.apache.openjpa.jdbc.meta.ReverseCustomizer</classname> plugin
-interface allows you to customze the reverse mapping process. See the class
+interface allows you to customize the reverse mapping process. See the class
 <ulink url="../javadoc/org/apache/openjpa/jdbc/meta/ReverseCustomizer.html">
 Javadoc</ulink> for details on the hooks that this interface provides. Specify
 the concrete plugin implementation to use with the <literal>
@@ -1118,7 +1119,7 @@
 name. It is a comma-separated list of key/value pairs, where each key is a
 possible field type, and each value is itself a plugin string describing the
 strategy for that type. We present an example below. See
-<xref linkend="ref_guide_mapping_custom_field"/> for information on custum
+<xref linkend="ref_guide_mapping_custom_field"/> for information on custom
 field strategies.
                         </para>
                     </listitem>
@@ -1137,8 +1138,8 @@
                     </listitem>
                     <listitem>
                         <para>
-<literal>JoinForeignKeyDeleteAction</literal>: The defualt delete action of
-foreign keys that join join secondary, collection, map, or subclass tables to
+<literal>JoinForeignKeyDeleteAction</literal>: The default delete action of
+foreign keys that join secondary, collection, map, or subclass tables to
 the primary table. Accepts the same values as the <literal>
 ForeignKeyDeleteAction</literal> property above.
                         </para>
@@ -1808,7 +1809,7 @@
 default mappings of an embeddable class. The JPA Overview details this process
 in <xref linkend="jpa_overview_mapping_embed"/>. <classname>
 AttributeOverride</classname>s suffice for simple mappings, but do not allow
-you to override complex mappings. Also, JPA has no way to differentitate between
+you to override complex mappings. Also, JPA has no way to differentiate between
 a null embedded object and one with default values for all of its fields.
             </para>
             <para>
@@ -1861,7 +1862,7 @@
 with <classname> AttributeOverride</classname> and <classname>
 AssociationOverride</classname> s. The <classname>MappingOverrides</classname>
 annotation, whose value is an array of <classname>MappingOverride</classname>
s,
-allows you to overide multiple mapped superclass mappings.
+allows you to override multiple mapped superclass mappings.
             </para>
             <para>
 Each
@@ -2412,7 +2413,7 @@
                 <para>
 The <ulink url="../javadoc/org/apache/openjpa/persistence/jdbc/Unique.html">
 <classname>org.apache.openjpa.persistence.jdbc.Unique</classname></ulink>
-annotation represents a unqiue constraint on the columns of a field. It is more
+annotation represents a unique constraint on the columns of a field. It is more
 convenient than using the <literal>uniqueConstraints</literal> property of
 standard JPA <classname>Table</classname> and <classname>SecondaryTable
 </classname> annotations, because you can apply it directly to the constrained
@@ -2461,7 +2462,7 @@
               </indexterm>
               <para>
 DB2, Oracle and SQLServer support XML column types and
-XPath queries and indexes over these columns.OpenJPA supports mapping of an
+XPath queries and indexes over these columns. OpenJPA supports mapping of an
 entity property mapped to an XML column.
               </para>
               <para>
@@ -2480,7 +2481,7 @@
               <para>
 The entity property class is required to have
 jaxb binding annotations.  This is produced when the classes are generated
-from an xml schema using the jaxb generator XJC.Ensure that <classname>@XmlRootElement</classname>
+from an XML schema using the jaxb generator XJC.Ensure that <classname>@XmlRootElement</classname>
 appears in the root class. In some case this annotation needs to be added manually if it
is missing.
               </para>
               <para>
@@ -2496,7 +2497,7 @@
 XML functions.
               </para>
               <para>
-The path expression must be single valued.Path expressions over xml
+The path expression must be single valued. Path expressions over XML
 mapped classes can only be used in WHERE as an operand to a simple predicate
 (=  &lt;&gt;  &lt;  &gt;  &gt;=  &lt;=).
               </para>
@@ -2527,7 +2528,7 @@
               </itemizedlist>
               <para>
 XML schema must not contain namespace declarations. The EJB query path
-expressions can not refer to java fields generated from XML ANY type or
+expressions can not refer to Java fields generated from XML ANY type or
 XML mixed element types.
               </para>
               <para>
@@ -2877,7 +2878,7 @@
 
 @Entity
 @Table(name="AUTH")
-@DataStoreIdColumn(name="AID" columnDefinition="INTEGER64")
+@DataStoreIdColumn(name="AID", columnDefinition="INTEGER64")
 public class Author {
     ...
 }
@@ -3233,7 +3234,7 @@
 you may need to consider both foreign key values and the expected class of the
 related object - for example, if you have an inverse relation that shares the
 foreign key with another inverse relation to an object of a different subclass.
-In these cases, set the proper class critera extension to <literal>true
+In these cases, set the proper class criteria extension to <literal>true
 </literal> to force OpenJPA to append class criteria to its select SQL.
                 </para>
                 <para>
@@ -3482,7 +3483,7 @@
         <para>
 Unless you apply database foreign key constraints extensively, it is possible to
 end up with orphaned keys in your database. For example, suppose <classname>
-Magazine</classname><literal>m</literal> has a reference to <classname>Article
+Magazine</classname> <literal>m</literal> has a reference to <classname>Article
 </classname><literal>a</literal>. If you delete <literal>a</literal>
without
 nulling <literal>m</literal>'s reference, <literal>m</literal>'s
database
 record will wind up with an orphaned key to the non-existent <literal>a

Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml Wed Oct 29 11:36:39 2008
@@ -502,7 +502,7 @@
 The OpenJPA <link linkend="ref_guide_pc_enhance">enhancer</link> may add a
 synthetic field to detachable classes to hold detached state (see
 <xref linkend="ref_guide_detach_graph"/> for details). You can instead
-declare your own detached state field or supress the creation of a detached
+declare your own detached state field or suppress the creation of a detached
 state field altogether. In the latter case, your class must not use
 <link linkend="ref_guide_pc_oid">datastore identity</link>, and should declare
 a version field to detect optimistic concurrency errors during detached
@@ -685,7 +685,7 @@
                 </indexterm>
                 <para>
 This extension names the inverse field in a logical bidirectional relation.
-To create a logical bidrectional relation in OpenJPA, use the
+To create a logical bidirectional relation in OpenJPA, use the
 <ulink url="../javadoc/org/apache/openjpa/persistence/InverseLogical.html">
 <classname>org.apache.openjpa.persistence.InverseLogical</classname></ulink>
 annotation. We discuss logical bidirectional relations and this

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=708975&r1=708974&r2=708975&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 Wed Oct 29 11:36:39
2008
@@ -256,7 +256,7 @@
                         <para>
 The default setting of <literal>on-demand</literal> minimizes the amount of time
 that OpenJPA holds onto a datastore connection. This is generally the best
-option from a scalability standpoind, as database resources are held for a
+option from a scalability standpoint, as database resources are held for a
 minimal amount of time. However, if you are not using connection pooling, or
 if your <classname>DataSource</classname> is not efficient at managing its
 pool, then this default value could cause undesirable pool contention.

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=708975&r1=708974&r2=708975&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 Wed Oct 29 11:36:39 2008
@@ -332,7 +332,7 @@
 <xref linkend="ref_guide_conf_plugins"/>). The agent accepts the long
 form of any of the standard configuration options
 (<xref linkend="ref_guide_conf_devtools"/> ). It also accepts the following
-options, the first three of which correspond exactly to to the same-named
+options, the first three of which correspond exactly to the same-named
 options of the enhancer tool described in
 <xref linkend="ref_guide_pc_enhance_build"/>:
             </para>
@@ -436,7 +436,7 @@
 runtime enhancement process for some reason.
                 </para></listitem>
                 <listitem><para>
-<emphasis>Runtime Unenhanced Classes</emphasis>: AKA statte comparison and 
+<emphasis>Runtime Unenhanced Classes</emphasis>: AKA state comparison and 
 subclassing. If you are running
 in a Java 5 environment without a javaagent, or in a Java 6 environment that
 does not support class retransformation, OpenJPA will still create subclasses
@@ -1141,7 +1141,7 @@
 version 1.3, the <methodname>set()</methodname> method cannot be overridden,
so
 when altering the calendar using that method, the field must be explicitly
 marked as dirty. This limitation does not apply when running with Java version
-1.4 and higer.
+1.4 and higher.
                 </para>
             </note>
         </section>
@@ -1674,7 +1674,7 @@
 that a field can externalize to something as simple as a primitive, something as
 complex as a collection or map of entities, or anything in
 between. If you do choose to externalize to a collection or map, OpenJPA
-recognizes a family of metadata extensions for specying type information for the
+recognizes a family of metadata extensions for specifying type information for the
 externalized form of your fields - see <xref linkend="type"/>. If the
 external form of your field is an entity object or contains entities, OpenJPA 
 will correctly include the objects in its persistence-by-reachability 
@@ -1841,7 +1841,7 @@
             </primary>
         </indexterm>
         <para>
-Fetch groups are sets of fields that load together. They can be used to to pool
+Fetch groups are sets of fields that load together. They can be used to pool
 together associated fields in order to provide performance improvements over
 standard data fetching. Specifying fetch groups allows for tuning of lazy
 loading and eager fetching behavior.

Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_remote.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_remote.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_remote.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_remote.xml Wed Oct 29 11:36:39
2008
@@ -130,7 +130,7 @@
         <listitem>
             <para>
                 Invoke <methodname>EntityTransaction.setRollbackOnly
-                </methodname> prior to detachingyour objects. Setting the 
+                </methodname> prior to detaching your objects. Setting the 
                 <literal>RollbackOnly</literal> flag prevents OpenJPA from 
                 flushing when detaching dirty objects; instead OpenJPA just 
                 runs its pre-flush actions (see the 
@@ -638,7 +638,7 @@
                     <listitem>
                         <para>
 <literal>NumBroadcastThreads</literal>: The number of threads to create for the
-purpose of transmitting events to peers. You sould increase this value as the
+purpose of transmitting events to peers. You should increase this value as the
 number of concurrent transactions increases. The maximum number of concurrent
 transactions is a function of the size of the connection pool. See the
 <literal>MaxActive</literal> property of <literal>

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=708975&r1=708974&r2=708975&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 Wed Oct 29 11:36:39
2008
@@ -737,7 +737,7 @@
 write locks.
                     </para>
                     <para>
-The <literal>pessimistic</literal> LockManager can be configued to additionally
+The <literal>pessimistic</literal> LockManager can be configured to additionally
 perform the version checking and incrementing behavior of the <literal>version
 </literal> lock manager described below by setting its <literal>
 VersionCheckOnReadLock</literal> and <literal>VersionUpdateOnWriteLock</literal>
@@ -932,7 +932,7 @@
 after a specific savepoint, then commit or continue making new changes in the
 transaction. This feature is useful for multi-stage transactions, such as
 editing a set of objects over several web pages or user screens. Savepoints also
-provide more flexibilty to conditional transaction behavior, such as choosing to
+provide more flexibility to conditional transaction behavior, such as choosing to
 commit or rollback a portion of the transaction based on the results of the
 changes. This chapter describes how to use and configure OpenJPA savepoints.
         </para>
@@ -1024,7 +1024,7 @@
 OpenJPA uses the 
 <ulink url="../javadoc/org/apache/openjpa/kernel/SavepointManager">
 <classname>org.apache.openjpa.kernel.SavepointManager</classname></ulink>
-<link linkend="ref_guide_conf_plugins">plugin</link> to handle perserving the
+<link linkend="ref_guide_conf_plugins">plugin</link> to handle preserving the
 savepoint state. OpenJPA includes the following <classname>SavepointManager
 </classname> plugins:
             </para>

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=708975&r1=708974&r2=708975&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 Wed Oct 29 11:36:39 2008
@@ -58,18 +58,18 @@
          <section><title>Transparency</title>
             <para>
 			  The primary design objective for Slice is to make the user 
-			  application transparent to the change in storage stratgey where 
+			  application transparent to the change in storage strategy where 
 			  data resides in multiple (possibly heterogeneous) databases instead
 			  of a single database. Slice achieves this transparency by 
 			  virtualization of multiple databases as a single database such 
-			  that OpenJPA object management kernel continues to intract in
+			  that OpenJPA object management kernel continues to interact in
 			  exactly the same manner with storage layer. Similarly, 
               the existing application or the persistent domain model requires 
               <emphasis>no change</emphasis> to upgrade from a single database

               to a distributed database environment. 
             </para>
 			<para>
-			  An existing application developed for a single databse can be 
+			  An existing application developed for a single database can be 
 			  adapted to work with multiple databases purely by configuring
 			  a persistence unit via <classname>META-INF/persistence.xml</classname>.

 			</para>
@@ -89,7 +89,7 @@
 			where the data is naturally amenable to horizontal partitions, 
 			for example, by temporal interval (e.g. Purchase Orders per month) 
 			or by geographical regions (e.g. Customer by Zip Code) can derive
-			singnificant performance benefit and favorable scaling behavior by 
+			significant performance benefit and favorable scaling behavior by 
 			using Slice.     
 			</para>
 		</section>
@@ -109,9 +109,9 @@
             </para>
          
             <para>
-            By deafult, any query is executed against all available slices. 
+            By default, any query is executed against all available slices. 
 			However, the application can target the query only to a subset of 
-			slices vy setting <emphasis>hint</emphasis> on <classname>javax.persistence.Query</classname>.

+			slices by setting <emphasis>hint</emphasis> on <classname>javax.persistence.Query</classname>.

 			The hint key is  <classname>openjpa.hint.slice.Target</classname> and 
             hint value is a comma-separated list of slice identifiers. The following 
             example shows how to target a query only to a pair of slices 
@@ -124,7 +124,7 @@
               Query query = em.createQuery("SELECT p FROM PObject")
 				              .setHint(hint, "One, Two");
               List result = query.getResultList();
-              // verify that each instance is originaing from the hinted slices
+              // verify that each instance is originating from the hinted slices
               for (Object pc : result) {
                  String sliceOrigin = SlicePersistence.getSlice(pc);
                  assertTrue ("One".equals(sliceOrigin) || "Two".equals(sliceOrigin));
@@ -167,7 +167,7 @@
 			 
 		 <para>
 			 Slice runtime invokes this user-supplied method for the newly
-			 persistent instance that are explict argument of the 
+			 persistent instance that is explicit argument of the 
 			 <classname>javax.persistence.EntityManager.persist(Object pc)</classname>
 			 method. The user application must return a valid slice name from
 			 this method to designate the target slice for the given instance.
@@ -183,7 +183,7 @@
              
 		<para>
 			The user application needs to specify the target slice <emphasis>only</emphasis>
-			for the <emphasis>root</emphasis> instance i.e. the explict argument for the
+			for the <emphasis>root</emphasis> instance i.e. the explicit argument for
the
 			<classname>EntityManager.persist(Object pc)</classname> method. Slice computes
 			the transitive closure of the graph i.e. the set of all instances 
 			directly or indirectly reachable from the root instance and stores
@@ -270,7 +270,7 @@
             No relationship can exist across database slices. In O-R mapping parlance,
             this condition translates to the limitation that the transitive closure of an
object graph must be 
             <emphasis>collocated</emphasis> in the same database.
-            For example, consider a domain model where Person relates to Adress.
+            For example, consider a domain model where Person relates to Address.
             Person X refers to Address A while Person Y refers to Address B. 
             Collocation Constraint means that <emphasis>both</emphasis> X and
A 
             must be stored in the same
@@ -431,7 +431,7 @@
 		<para>
 			The entities that are annotated with <classname>@Replicated</classname> 
 			annotation can be stored in multiple slices as identical copies.
-        Specify the implementation class of <classname>ReplicationPolicy</classname>in
configuration as
+        Specify the implementation class of <classname>ReplicationPolicy</classname>
in configuration as
         <programlisting> 
          <![CDATA[ <property name="openjpa.slice.ReplicationPolicy" value="com.acme.foo.MyReplicationPolicy"/>]]>
         </programlisting>
@@ -485,14 +485,14 @@
 		 <para>
 			 The user application often directs OpenJPA to generate primary keys 
 			 for persistence instances automatically or from a specific database 
-			 sequence. For such primary key value generation startegy where 
+			 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. 
 		 </para>
          <para>
-			 The master slice can be specified explictly via 
+			 The master slice can be specified explicitly via 
 			 <classname>openjpa.slice.Master</classname> property and whose value is one
-			 of the configured slice name. If this property is not explictly
+			 of the configured slice names. If this property is not explicitly
 			 specified then, by default, the master slice is the first slice 
 			 in the list of configured slice names. 
        </para>

Modified: openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml?rev=708975&r1=708974&r2=708975&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml Wed Oct 29 11:36:39
2008
@@ -1002,7 +1002,7 @@
                 <listitem>
                     <para>
 Persisting a zero-length string results in a string with a single space
-characted being returned from Sybase, Inc.'s JDBC driver.
+character being returned from Sybase, Inc.'s JDBC driver.
                     </para>
                 </listitem>
                 <listitem>
@@ -1016,11 +1016,11 @@
                 </listitem>
                 <listitem>
                     <para> 
-Applications performing update/insert data of the BigDecimal java type may fail 
+Applications performing update/insert data of the BigDecimal Java type may fail 
 with OptimisticException if the data exceeds the scale or precision of the
 column on Sybase. To avoid this problem, applications can specify the precision
 and scale for the numeric type by setting numericTypeName='NUMERIC(p,s)' for
-the column type mapped by the BigDecimal java type. See
+the column type mapped by the BigDecimal Java type. See
 <link linkend="openjpa.jdbc.DBDictionary">openjpa.jdbc.DBDictionary</link> for
 more detail. Alternatively, application can set the precision and scale using
 the standard <classname>Column</classname> annotation, described in



Mime
View raw message