Author: mtylenda
Date: Sat Jun 6 09:06:32 2009
New Revision: 782212
URL: http://svn.apache.org/viewvc?rev=782212&view=rev
Log:
OPENJPA-1127: Typos in user manual and log messages
Modified:
openjpa/trunk/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/localizer.properties
openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_query.xml
openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml
openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml
openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml
Modified:
openjpa/trunk/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/localizer.properties
URL:
http://svn.apache.org/viewvc/openjpa/trunk/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/localizer.properties?rev=782212&r1=782211&r2=782212&view=diff
==============================================================================
---
openjpa/trunk/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/localizer.properties
(original)
+++
openjpa/trunk/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/localizer.properties
Sat Jun 6 09:06:32 2009
@@ -194,7 +194,7 @@
field_name must be specified in the orederBy item of the orderBy list \
for "{0}".
dynamic-agent: OpenJPA dynamically loaded the class enhancer. Any classes \
- that were not enhanced at build time will be enhanced when the are \
+ that were not enhanced at build time will be enhanced when they are \
loaded by the JVM.
vlem-creation-warn: Could not create the optional validation provider. \
Reason returned: "{0}"
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=782212&r1=782211&r2=782212&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 Sat Jun
6 09:06:32 2009
@@ -646,7 +646,7 @@
</title>
<para>
JPQL provides support for hints which are name/value pairs used to control
locking and optimization keywords in sql.
-The following example shows how to use the JPA hint api to set the
<classname>ReadLockMode</classname> and <classname>ResultCount</classname> in
the OpenJPA fetch plan. This will result in the sql keywords OPTIMIZE FOR 2
ROWS and UPDATE to be emitted into the sql provided that a pessimistic
LockManager is being used.
+The following example shows how to use the JPA hint api to set the
<classname>ReadLockMode</classname> and <classname>ResultCount</classname> in
the OpenJPA fetch plan. This will result in the sql keywords OPTIMIZE FOR 2
ROWS and FOR UPDATE to be emitted into the sql provided that a pessimistic
LockManager is being used.
</para>
<example id="jpa_query_hint1">
<title>
@@ -2519,10 +2519,10 @@
</title>
<para>
<itemizedlist><listitem><para>functions_returning_strings ::=
-CONCAT(string_primar y, string_primary) | SUBSTRING(string_primar y,
+CONCAT(string_primary, string_primary) | SUBSTRING(string_primary,
simple_arithmetic_expression, simple_arithmetic_expression) |
TRIM([[trim_specification] [trim_character] FROM] string_primary) |
-LOWER(string_primar y) | UPPER(string_primar y)
+LOWER(string_primary) | UPPER(string_primary)
</para>
</listitem>
<listitem>
@@ -2532,8 +2532,8 @@
</listitem>
<listitem>
<para>
-functions_returning_numerics ::= LENGTH(string_primar y) | LOCATE(string_primar
-y, string_primar y[, simple_arithmetic_expression])
+functions_returning_numerics ::= LENGTH(string_primary) |
+LOCATE(string_primary, string_primary[, simple_arithmetic_expression])
</para>
</listitem>
</itemizedlist>
Modified: openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml
URL:
http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml?rev=782212&r1=782211&r2=782212&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml
(original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_caching.xml Sat Jun
6 09:06:32 2009
@@ -117,7 +117,7 @@
are loaded from the datastore.
</para>
<para>
-OpenJPA's data cache can in both single-JVM and multi-JVM environments.
+OpenJPA's data cache can operate in both single-JVM and multi-JVM environments.
Multi-JVM caching is achieved through the use of the distributed event
notification framework described in <xref linkend="ref_guide_event"/>, or
through custom integrations with a third-party distributed cache.
@@ -322,7 +322,7 @@
<example id="ref_guide_cache_use_jpa_standard">
<title>Using the javax.persistence.Cache interface</title>
<programlisting>
-// Check whether the cache contains a entity with a provided ID
+// Check whether the cache contains an entity with a provided ID
Cache cache = em.getCache();
boolean contains = cache.contains(MyEntity.class, entityID);
@@ -1048,7 +1048,7 @@
<para>
Prepared SQL Cache is configured by the <link
linkend="openjpa.jdbc.QuerySQLCache">
<literal>openjpa.jdbc.QuerySQLCache</literal></link> configuration property.
This
-property accepts a a plugin string (see <xref
linkend="ref_guide_conf_plugins"/>)
+property accepts a plugin string (see <xref linkend="ref_guide_conf_plugins"/>)
with value of <literal>true</literal> or <literal>false</literal>. The default
is <literal>true</literal>.
</para>
@@ -1082,7 +1082,7 @@
same as the first, though both will result in same SQL statement.
</para>
<para>
- While in <xref linkend="jpa_caching_parametrize_jpql"></xref>, the the
+ While in <xref linkend="jpa_caching_parametrize_jpql"></xref>, the
selection value for the <code>p.name</code> field is parameterized.
Prepared Query Cache will recognize the second execution as
same as the first, and will execute the cached SQL statement directly.
@@ -1137,7 +1137,7 @@
<itemizedlist>
<listitem>A user application can disable Prepared SQL Cache
for entire lifetime of a persistence context by invoking the following
- method on OpenJPA's EntityMananger interface:
+ method on OpenJPA's EntityManager interface:
<programlisting>
<methodname>OpenJPAEntityManager.setQuerySQLCache(boolean)</methodname>
</programlisting>
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=782212&r1=782211&r2=782212&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 Sat Jun
6 09:06:32 2009
@@ -2098,7 +2098,7 @@
</indexterm>
<literal>StoreLargeNumbersAsStrings</literal>: When true, the dictionary
prefers to store Java fields of
-type <classname>BigInteger</classname> and <classname>BigDecimal</classname>)
+type <classname>BigInteger</classname> and <classname>BigDecimal</classname>
as string values in the database. Likewise, the dictionary will instruct
the mapping tool to map these Java types to character columns.
Because some databases have limitations on the number of digits that can
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=782212&r1=782211&r2=782212&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 Jun 6
09:06:32 2009
@@ -421,7 +421,7 @@
When then dynamic enhancer is loaded, the following
informational message is logged:
<programlisting>
-[java] jpa.enhancement INFO [main] openjpa.Runtime - OpenJPA dynamically
loaded the class enhancer. Any classes that were not enhanced at build time
will be enhanced as they are loaded by the JVM.
+[java] jpa.enhancement INFO [main] openjpa.Runtime - OpenJPA dynamically
loaded the class enhancer. Any classes that were not enhanced at build time
will be enhanced when they are loaded by the JVM.
</programlisting>
</para>
<para>
@@ -730,7 +730,7 @@
/**
* LineItem uses a compound primary key. Part of the compound key
- * LineItemId is relation or refernce to Order instance.
+ * LineItemId is relation or reference to Order instance.
**/
@Entity
@IdClass(LineItemId.class)
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=782212&r1=782211&r2=782212&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml
(original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml Sat
Jun 6 09:06:32 2009
@@ -365,8 +365,8 @@
</listitem>
<listitem>
<para>
-Interbase does not support the <literal>LOWER</literal>, <literal>SUBSTRING
-</literal>, or <literal>INSTR</literal> SQL functions>
+Interbase does not support the <literal>LOWER</literal>,
+<literal>SUBSTRING</literal>, or <literal>INSTR</literal> SQL functions.
</para>
</listitem>
</itemizedlist>
@@ -823,7 +823,7 @@
<para>
When using large result sets with MySQL there are a number of documented
limitations.
Please read the section titled "ResultSet" in the "MySQL JDBC API
Implementation Notes".
-The net of these limitations is that you will have to read all of the rows of a
+The net effect of these limitations is that you will have to read all of the
rows of a
result set (or close the connection) before you can issue any other queries on
the connection, or an exception will be thrown. Setting openjpa.FetchBatchSize
to any value greater than zero will enable streaming result sets.
