From cdfb5c79c50d56c305c8d02e620149440ebc7b80 Mon Sep 17 00:00:00 2001 From: Milosz Tylenda Date: Sun, 6 Feb 2011 19:03:15 +0000 Subject: [PATCH] OPENJPA-1932: Sun -> Oracle, update copyright year, make LOB term consistent in case, fix typos. git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@1067730 13f79535-47bb-0310-9956-ffa450edef68 --- openjpa-project/src/doc/manual/jpa_overview_intro.xml | 4 ++-- openjpa-project/src/doc/manual/jpa_overview_query.xml | 4 ++-- openjpa-project/src/doc/manual/openjpa_intro.xml | 2 +- openjpa-project/src/doc/manual/openjpa_legal.xml | 8 +++++--- openjpa-project/src/doc/manual/ref_guide_optimization.xml | 2 +- openjpa-project/src/doc/manual/ref_guide_pc.xml | 2 +- openjpa-project/src/doc/manual/ref_guide_slice.xml | 7 +++---- openjpa-project/src/doc/manual/supported_databases.xml | 4 ++-- 8 files changed, 17 insertions(+), 16 deletions(-) diff --git a/openjpa-project/src/doc/manual/jpa_overview_intro.xml b/openjpa-project/src/doc/manual/jpa_overview_intro.xml index 146fcdcd5..df7ee6c4f 100644 --- a/openjpa-project/src/doc/manual/jpa_overview_intro.xml +++ b/openjpa-project/src/doc/manual/jpa_overview_intro.xml @@ -35,8 +35,8 @@ JPA -The Java Persistence API (JPA) is a specification from -Sun Microsystems for the persistence of Java objects to any relational +The Java Persistence API (JPA) is a specification +for the persistence of Java objects to any relational datastore. JPA requires J2SE 1.5 (also referred to as "Java 5") or higher, as it makes heavy use of new Java language features such as annotations and generics. This document provides an overview of JPA. Unless diff --git a/openjpa-project/src/doc/manual/jpa_overview_query.xml b/openjpa-project/src/doc/manual/jpa_overview_query.xml index f42b3a29d..ef84bf291 100644 --- a/openjpa-project/src/doc/manual/jpa_overview_query.xml +++ b/openjpa-project/src/doc/manual/jpa_overview_query.xml @@ -2531,7 +2531,7 @@ HAVING clause. State-fields that are mapped in serialized form or as -lobs may not be portably used in conditional expressions. The +LOBs may not be portably used in conditional expressions. The implementation is not expected to perform such query operations involving such fields in memory rather than in the database. @@ -3614,7 +3614,7 @@ the groups, null values are treated as the same for grouping purposes. Grouping by an entity is permitted. In this case, the entity must contain no serialized -state fields or lob-valued state fields that are eagerly fetched. +state fields or LOB-valued state fields that are eagerly fetched. Grouping by embeddables is not supported. diff --git a/openjpa-project/src/doc/manual/openjpa_intro.xml b/openjpa-project/src/doc/manual/openjpa_intro.xml index 0901d0ae9..1dcd6474c 100644 --- a/openjpa-project/src/doc/manual/openjpa_intro.xml +++ b/openjpa-project/src/doc/manual/openjpa_intro.xml @@ -27,7 +27,7 @@ -OpenJPA is Apache's implementation of Sun's Java Persistence 2.0 API +OpenJPA is Apache's implementation of Java Persistence 2.0 API (JSR-317 JPA 2.0) specification for the transparent persistence of Java objects. This document provides an overview of the JPA standard and technical details on the use of OpenJPA. diff --git a/openjpa-project/src/doc/manual/openjpa_legal.xml b/openjpa-project/src/doc/manual/openjpa_legal.xml index e8352f369..ef717d3a0 100644 --- a/openjpa-project/src/doc/manual/openjpa_legal.xml +++ b/openjpa-project/src/doc/manual/openjpa_legal.xml @@ -93,12 +93,10 @@ The openjpa-all aggregate JAR includes software developed by the: diff --git a/openjpa-project/src/doc/manual/ref_guide_optimization.xml b/openjpa-project/src/doc/manual/ref_guide_optimization.xml index 9d772f497..989f88c02 100644 --- a/openjpa-project/src/doc/manual/ref_guide_optimization.xml +++ b/openjpa-project/src/doc/manual/ref_guide_optimization.xml @@ -123,7 +123,7 @@ or deletes. Manipulating various parameters of the Java Virtual Machine (such as hotspot compilation modes and the maximum memory) can result in performance improvements. For more details about optimizing the JVM execution environment, -please see . +please see . diff --git a/openjpa-project/src/doc/manual/ref_guide_pc.xml b/openjpa-project/src/doc/manual/ref_guide_pc.xml index acd7a667f..ce7b7bd43 100644 --- a/openjpa-project/src/doc/manual/ref_guide_pc.xml +++ b/openjpa-project/src/doc/manual/ref_guide_pc.xml @@ -386,7 +386,7 @@ java -javaagent:/home/dev/openjpa/lib/openjpa.jar=addDefaultConstructor=false co If a javaagent is not provided via the command line and - OpenJPA is running on the Sun 1.6 SDK or IBM 1.6 JDK (SR8+), OpenJPA + OpenJPA is running on the Oracle 1.6 SDK or IBM 1.6 JDK (SR8+), OpenJPA will attempt to dynamically load the Enhancer that was mentioned in the previous section. This support is provided as an ease of use feature and it is not recommended diff --git a/openjpa-project/src/doc/manual/ref_guide_slice.xml b/openjpa-project/src/doc/manual/ref_guide_slice.xml index 7128e08aa..974efe66e 100644 --- a/openjpa-project/src/doc/manual/ref_guide_slice.xml +++ b/openjpa-project/src/doc/manual/ref_guide_slice.xml @@ -136,11 +136,11 @@ To confine queries to a subset of slices via setting query hints can be considered intrusive to existing application. The alternative means of targeting queries is to - a configure a Query Target Policy. This policy is configured + configure a Query Target Policy. This policy is configured via plug-in property openjpa.slice.QueryTargetPolicy. The - plug-in property is fully-qualified class name an implementation + plug-in property is fully-qualified class name of an implementation for org.apache.openjpa.slice.QueryTargetPolicy interface. - This interface contract allows an user application to target a query select a subset + This interface contract allows a user application to target a query to a subset of slices based on the query and its bound parameters. The query target policy is consulted only when no explicit target hint is set on the query. By default, the policy executes a query on all available slices. @@ -152,7 +152,6 @@ by primary key. This finder target policy is consulted only when no explicit target hint is set on the current fetch plan. By default, the policy executes a query on all available slices to find an instance by its primary key. - To confine queries to a subset of slices via setting query hints can be considered diff --git a/openjpa-project/src/doc/manual/supported_databases.xml b/openjpa-project/src/doc/manual/supported_databases.xml index c65b746ab..00c9aa4ba 100644 --- a/openjpa-project/src/doc/manual/supported_databases.xml +++ b/openjpa-project/src/doc/manual/supported_databases.xml @@ -715,8 +715,8 @@ See DB2 for z/OS documentation for additional information. When using LOBs with persistent attributes of a streaming data type (e.g. -java.io.InputStream) in the case of very large lob, DB2 JCC -driver will automatically use progressive streaming to retrieve the Lob data. +java.io.InputStream) in the case of very large LOB, DB2 JCC +driver will automatically use progressive streaming to retrieve the LOB data. With progressiveStreaming, the inputStream retrieved must be fully materialized before the next iteration of call to rs.next(). By default this will result in a LobClosedException when OpenJPA processes the InputStream.