openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mik...@apache.org
Subject svn commit: r757388 [3/7] - in /openjpa/trunk: openjpa-examples/src/main/java/ openjpa-examples/src/main/java/META-INF/ openjpa-examples/src/main/java/hellojpa/ openjpa-examples/src/main/java/relations/ openjpa-jdbc/src/main/resources/org/apache/openjp...
Date Mon, 23 Mar 2009 12:42:46 GMT
Modified: openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/meta/common/apps/META-INF/persistence.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/meta/common/apps/META-INF/persistence.xml?rev=757388&r1=757387&r2=757388&view=diff
==============================================================================
--- openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/meta/common/apps/META-INF/persistence.xml (original)
+++ openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/meta/common/apps/META-INF/persistence.xml Mon Mar 23 12:42:41 2009
@@ -1,47 +1,47 @@
-<!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements.  See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership.  The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License.  You may obtain a copy of the License at
- 
- http://www.apache.org/licenses/LICENSE-2.0
- 
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied.  See the License for the
- specific language governing permissions and limitations
- under the License.   
--->
-<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
-    http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0">
-
-	<persistence-unit name="TestConv" transaction-type="RESOURCE_LOCAL">
-		<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
-		<class>org.apache.openjpa.persistence.meta.common.apps.ExternalValues</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.FieldOrderPC</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.FieldOrderPCSubclass</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest1</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest1$Inner</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest2</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest3</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest4</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest5</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest6</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.NonPersistentFieldsPC</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.OrderByPC</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.OrderByPCRel</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.OrderByPCRelSub</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.RuntimeTest1</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.RuntimeTest2</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.RuntimeTest3</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.SequenceAssigned</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.SequenceAssigned2</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.SequenceAssigned3</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.ValueStrategyPC</class>
-		<class>org.apache.openjpa.persistence.meta.common.apps.TransactionalClassPC</class>
-	</persistence-unit>
-</persistence>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+ http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.   
+-->
+<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
+    http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0">
+
+	<persistence-unit name="TestConv" transaction-type="RESOURCE_LOCAL">
+		<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
+		<class>org.apache.openjpa.persistence.meta.common.apps.ExternalValues</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.FieldOrderPC</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.FieldOrderPCSubclass</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest1</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest1$Inner</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest2</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest3</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest4</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest5</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.MetaTest6</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.NonPersistentFieldsPC</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.OrderByPC</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.OrderByPCRel</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.OrderByPCRelSub</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.RuntimeTest1</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.RuntimeTest2</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.RuntimeTest3</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.SequenceAssigned</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.SequenceAssigned2</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.SequenceAssigned3</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.ValueStrategyPC</class>
+		<class>org.apache.openjpa.persistence.meta.common.apps.TransactionalClassPC</class>
+	</persistence-unit>
+</persistence>

Propchange: openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/meta/common/apps/META-INF/persistence.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/query/common/apps/META-INF/persistence.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/query/common/apps/META-INF/persistence.xml?rev=757388&r1=757387&r2=757388&view=diff
==============================================================================
--- openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/query/common/apps/META-INF/persistence.xml (original)
+++ openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/query/common/apps/META-INF/persistence.xml Mon Mar 23 12:42:41 2009
@@ -1,50 +1,50 @@
-<!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements.  See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership.  The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License.  You may obtain a copy of the License at
- 
- http://www.apache.org/licenses/LICENSE-2.0
- 
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied.  See the License for the
- specific language governing permissions and limitations
- under the License.   
--->
-<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
-    http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0">
-	<persistence-unit name="TestConv" transaction-type="RESOURCE_LOCAL">
-		<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
-        <class>org.apache.openjpa.persistence.query.common.apps.Entity1</class>
-        <class>org.apache.openjpa.persistence.query.common.apps.Entity2</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.RuntimeTest1</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.RuntimeTest2</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.RuntimeTest3</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.RuntimeTest4</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.RuntimeTest5</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.SimpleAppIdPC</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.CompoundAppIdPC</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.QueryTest1</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.QueryTest2</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.QueryTest3</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.QueryTest4</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.CompoundAppIdPC</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.ComplexA</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.ComplexB</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.ComplexC</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.ComplexD</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.ComplexE</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.ComplexF</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.ComplexG</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.CircularFKPC</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.CircularFKPC2</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.ModRuntimeTest1</class>
-		<class>org.apache.openjpa.persistence.query.common.apps.ModRuntimeTest2</class>
-        <class>org.apache.openjpa.persistence.query.common.apps.QTimeout</class>
-	</persistence-unit>
-</persistence>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+ http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.   
+-->
+<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
+    http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0">
+	<persistence-unit name="TestConv" transaction-type="RESOURCE_LOCAL">
+		<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
+        <class>org.apache.openjpa.persistence.query.common.apps.Entity1</class>
+        <class>org.apache.openjpa.persistence.query.common.apps.Entity2</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.RuntimeTest1</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.RuntimeTest2</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.RuntimeTest3</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.RuntimeTest4</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.RuntimeTest5</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.SimpleAppIdPC</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.CompoundAppIdPC</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.QueryTest1</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.QueryTest2</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.QueryTest3</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.QueryTest4</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.CompoundAppIdPC</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.ComplexA</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.ComplexB</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.ComplexC</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.ComplexD</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.ComplexE</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.ComplexF</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.ComplexG</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.CircularFKPC</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.CircularFKPC2</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.ModRuntimeTest1</class>
+		<class>org.apache.openjpa.persistence.query.common.apps.ModRuntimeTest2</class>
+        <class>org.apache.openjpa.persistence.query.common.apps.QTimeout</class>
+	</persistence-unit>
+</persistence>

Propchange: openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/query/common/apps/META-INF/persistence.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/xml/persistence-without-xsd.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/xml/persistence-without-xsd.xml?rev=757388&r1=757387&r2=757388&view=diff
==============================================================================
--- openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/xml/persistence-without-xsd.xml (original)
+++ openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/xml/persistence-without-xsd.xml Mon Mar 23 12:42:41 2009
@@ -1,28 +1,28 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements.  See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership.  The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License.  You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied.  See the License for the
- specific language governing permissions and limitations
- under the License.
--->
-<persistence>
-    <persistence-unit name="incorrect-ordering-and-no-xsd">
-        <properties>
-            <property name="openjpa.Id" value="incorrect-ordering-pu"/>
-        </properties>
-        <class>org.apache.openjpa.persistence.xml.SimpleXmlEntity</class>
-        <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
-    </persistence-unit>
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+<persistence>
+    <persistence-unit name="incorrect-ordering-and-no-xsd">
+        <properties>
+            <property name="openjpa.Id" value="incorrect-ordering-pu"/>
+        </properties>
+        <class>org.apache.openjpa.persistence.xml.SimpleXmlEntity</class>
+        <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
+    </persistence-unit>
 </persistence>
\ No newline at end of file

Propchange: openjpa/trunk/openjpa-persistence-jdbc/src/test/resources/org/apache/openjpa/persistence/xml/persistence-without-xsd.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: openjpa/trunk/openjpa-project/assembly.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/assembly.xml?rev=757388&r1=757387&r2=757388&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/assembly.xml (original)
+++ openjpa/trunk/openjpa-project/assembly.xml Mon Mar 23 12:42:41 2009
@@ -1,102 +1,102 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements.  See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership.  The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License.  You may obtain a copy of the License at
- 
- http://www.apache.org/licenses/LICENSE-2.0
- 
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied.  See the License for the
- specific language governing permissions and limitations
- under the License.   
--->
-<assembly>
-    <id>binary</id>
-    <formats>
-        <format>zip</format>
-    </formats>
-    <includeBaseDirectory>true</includeBaseDirectory>
-    <fileSets>
-        <fileSet>
-            <directory>target/aggregate</directory>
-            <outputDirectory>/</outputDirectory>
-        </fileSet>
-        <fileSet>
-            <includes>
-                <include>README</include>
-                <include>DISCLAIMER</include>
-                <include>LICENSE</include>
-                <include>STATUS</include>
-                <include>NOTICE</include>
-                <include>README.txt</include>
-                <include>DISCLAIMER.txt</include>
-                <include>LICENSE.txt</include>
-                <include>STATUS.txt</include>
-                <include>NOTICE.txt</include>
-                <include>RELEASE-NOTES</include>
-                <include>RELEASE-NOTES.html</include>
-                <include>RELEASE-NOTES.txt</include>
-                <include>CHANGES</include>
-                <include>CHANGES.txt</include>
-            </includes>
-        </fileSet>
-        <!--
-        <fileSet>
-            <directory>licenses</directory>
-            <outputDirectory>/lib</outputDirectory>
-            <includes>
-                <include>*</include>
-            </includes>
-        </fileSet>
-        <fileSet>
-            <directory>target/examples</directory>
-            <outputDirectory>/examples</outputDirectory>
-        </fileSet>
-        -->
-        <fileSet>
-            <directory>target/manual</directory>
-            <outputDirectory>docs/manual</outputDirectory>
-        </fileSet>
-        <fileSet>
-            <directory>../target/site/apidocs</directory>
-            <outputDirectory>docs/javadoc</outputDirectory>
-        </fileSet>
-        <fileSet>
-            <directory>../openjpa-examples/src/main/java</directory>
-            <outputDirectory>examples</outputDirectory>
-        </fileSet>
-    </fileSets>
-    <dependencySets>
-        <dependencySet>
-            <outputDirectory>/</outputDirectory>
-            <unpack>false</unpack>
-            <scope>runtime</scope>
-            <includes>
-                <include>org.apache.openjpa:openjpa</include>
-            </includes>
-        </dependencySet>
-        <dependencySet>
-            <outputDirectory>/lib</outputDirectory>
-            <unpack>false</unpack>
-            <scope>runtime</scope>
-            <includes>
-                <include>net.sourceforge.serp:serp</include>
-                <include>org.apache.derby:derby</include>
-
-                <include>commons-lang:commons-lang</include>
-                <include>commons-collections:commons-collections</include>
-                <include>commons-pool:commons-pool</include>
-
-                <include>org.apache.geronimo.specs:geronimo-jta_1.1_spec</include>
-                <include>org.apache.geronimo.specs:geronimo-jpa_2.0_spec</include>
-            </includes>
-        </dependencySet>
-    </dependencySets>
-</assembly>
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+ http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.   
+-->
+<assembly>
+    <id>binary</id>
+    <formats>
+        <format>zip</format>
+    </formats>
+    <includeBaseDirectory>true</includeBaseDirectory>
+    <fileSets>
+        <fileSet>
+            <directory>target/aggregate</directory>
+            <outputDirectory>/</outputDirectory>
+        </fileSet>
+        <fileSet>
+            <includes>
+                <include>README</include>
+                <include>DISCLAIMER</include>
+                <include>LICENSE</include>
+                <include>STATUS</include>
+                <include>NOTICE</include>
+                <include>README.txt</include>
+                <include>DISCLAIMER.txt</include>
+                <include>LICENSE.txt</include>
+                <include>STATUS.txt</include>
+                <include>NOTICE.txt</include>
+                <include>RELEASE-NOTES</include>
+                <include>RELEASE-NOTES.html</include>
+                <include>RELEASE-NOTES.txt</include>
+                <include>CHANGES</include>
+                <include>CHANGES.txt</include>
+            </includes>
+        </fileSet>
+        <!--
+        <fileSet>
+            <directory>licenses</directory>
+            <outputDirectory>/lib</outputDirectory>
+            <includes>
+                <include>*</include>
+            </includes>
+        </fileSet>
+        <fileSet>
+            <directory>target/examples</directory>
+            <outputDirectory>/examples</outputDirectory>
+        </fileSet>
+        -->
+        <fileSet>
+            <directory>target/manual</directory>
+            <outputDirectory>docs/manual</outputDirectory>
+        </fileSet>
+        <fileSet>
+            <directory>../target/site/apidocs</directory>
+            <outputDirectory>docs/javadoc</outputDirectory>
+        </fileSet>
+        <fileSet>
+            <directory>../openjpa-examples/src/main/java</directory>
+            <outputDirectory>examples</outputDirectory>
+        </fileSet>
+    </fileSets>
+    <dependencySets>
+        <dependencySet>
+            <outputDirectory>/</outputDirectory>
+            <unpack>false</unpack>
+            <scope>runtime</scope>
+            <includes>
+                <include>org.apache.openjpa:openjpa</include>
+            </includes>
+        </dependencySet>
+        <dependencySet>
+            <outputDirectory>/lib</outputDirectory>
+            <unpack>false</unpack>
+            <scope>runtime</scope>
+            <includes>
+                <include>net.sourceforge.serp:serp</include>
+                <include>org.apache.derby:derby</include>
+
+                <include>commons-lang:commons-lang</include>
+                <include>commons-collections:commons-collections</include>
+                <include>commons-pool:commons-pool</include>
+
+                <include>org.apache.geronimo.specs:geronimo-jta_1.1_spec</include>
+                <include>org.apache.geronimo.specs:geronimo-jpa_2.0_spec</include>
+            </includes>
+        </dependencySet>
+    </dependencySets>
+</assembly>

Propchange: openjpa/trunk/openjpa-project/assembly.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/source-assembly.xml
------------------------------------------------------------------------------
    svn:eol-style = native

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=757388&r1=757387&r2=757388&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 Mon Mar 23 12:42:41 2009
@@ -195,8 +195,8 @@
             Interaction of Interfaces Outside Container
         </title>
 <programlisting>
-  // get an EntityManagerFactory using the Persistence class
-  // It is not recommended to obtain a factory often, as construction of a
+  // get an EntityManagerFactory using the Persistence class
+  // It is not recommended to obtain a factory often, as construction of a
   // factory is a costly operation. Typically you will like to cache  
   // a factory and then refer it for repeated use
   EntityManagerFactory factory = Persistence.createEntityManagerFactory(null);
@@ -209,9 +209,9 @@
 
   // query for all employees who work in our research division
   // and put in over 40 hours a week average
-  Query query = em.createQuery("SELECT e " +
-                               "  FROM Employee e " +
-                               " WHERE e.division.name = 'Research' " +
+  Query query = em.createQuery("SELECT e " +
+                               "  FROM Employee e " +
+                               " WHERE e.division.name = 'Research' " +
                                "   AND e.avgHours &gt; 40");
   List results = query.getResultList ();
 
@@ -222,8 +222,8 @@
   }
 
   // commit will detect all updated entities and save them in database
-  em.getTransaction().commit();
-
+  em.getTransaction().commit();
+
   // free the resources
   em.close();
 </programlisting>

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_conclusion.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_criteria.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_criteria.xml?rev=757388&r1=757387&r2=757388&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_criteria.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_criteria.xml Mon Mar 23 12:42:41 2009
@@ -37,120 +37,120 @@
             Query
         </see>
     </indexterm>
-    <para>
-    JPA 2.0 Specification introduces a new API to define queries dynamically
-    via construction of an object-based 
-    <classname>javax.persistence.QueryDefinition</classname> instance, rather
-    than string-based approach used in JPQL (Java Persistence Query Language).
-    This dynamic query definition capability, referred as Criteria API, is 
-    based on the abstract persistent schema of the entities, their embedded
-    objects and their relationships. The syntax is designed to construct a
-    <emphasis>Query Tree</emphasis> whose nodes represent the semantic query
-    elements such as projections, conditional predicates of WHERE clause or
-    GROUP BY elements etc. 
-    </para>
-    
-    <section>
-    	<title>Constructing a QueryDefinition</title>
-    	<para>
-    	The QueryBuilder interface is the factory for QueryDefinition. A
-    	QueryBuilder is obtained from either the EntityManagerFactory or 
-    	the EntityManager as follows:
-    	<programlisting>
-EntityManager em = ... ; 
-QueryBuilder queryBuilder = em.getQueryBuilder();
-QueryDefinition qdef = queryBuilder.createQueryDefinition();
-    	</programlisting>
-    	The first step in constructing a query definition is specification of 
-    	query roots.  Query roots specify the domain objects on which the query 
-    	is evaluated. Query root is an instance of the DomainObject interface. A
-    	query root is added to a QueryDefinition by 
-    	<methodname>addRoot(Class c)</methodname> method.
-    	<programlisting>
-    	DomainObject customer = qdef.addRoot(Customer.class);
-    	</programlisting>
-    	Often a query definition has a single root, so the 
-    	QueryBuilder interface allows to construct and add
-    	a root via a single method.
-    	<programlisting>
-DomainObject customer = queryBuilder.createQueryDefinition(Customer.class);    	
-    	</programlisting>
-    	A query domain can be further refined by joining to other domain objects.
-    	For example, for the above query definition to operate over customers 
-    	and their orders, use <methodname>join(String attribute)</methodname>:
-		<programlisting>
-DomainObject order = customer.join("orders");
-		</programlisting>  
-		The condition of a query definition is set via 
-		<methodname>where(Predicate p)</methodname> where the argument 
-		designates a conditional predicate. Conditional predicates are often
-		composed of one or more comparisons between the attribute values of
-		the domain objects and some variable. For example, to select the
-		Customers whose name is <emphasis>John Doe</emphasis> and has 
-		orders that are not yet delivered, you can build the predicate and set  
-		it to the query definition as
-		<programlisting>
-qdef.where(customer.get("name").equal("John Doe")
-      .and(order.get("status").equal(OrderStatus.DELIVERED).not()));
-		</programlisting>
-		The <methodname>select()</methodname> method defines the result of the
-		query. If left unspecified, the select projection is assumed to be the
-		root domain object. However, you can specify the selected projections
-		explicitly as a list 
-		<programlisting>
-qdef.select(customer.get("name"), order.get("status"));
-		</programlisting>
-		Attribute of a domain object is specified by navigating via 
-		<methodname>get(String attr)</methodname>. The attribute 
-		<emphasis>should</emphasis> refer
-		to a valid persistent property of the receiving domain object, however
-		no such validation is enforced during the construction of the query 
-		definition. All validation is deferred till query is actually executed.
-    	</para>
-    </section> 
-    
-    <section>
-    <title>Executing a QueryDefinition</title>
-    <para>
-    A QueryDefinition is executed in a similar fashion of a string-based JPQL
-    query via the EntityManager and Query interfaces.
-    <programlisting>
-EntityManager em = ...
-Query query = em.createQuery(qdef);
-List result = query.getResultList();    
-    </programlisting>
-    </para>
-    <para>
-    A query definition can use named parameters, and the parameter values are
-    set as usual in the Query instance. 
-    </para>
-    
-    <para>
-    The JPA 2.0 Specification on Criteria API is evolving and hence for an
-    up-to-date version of the API, please consult the  
-    <ulink url="http://jcp.org/aboutJava/communityprocess/pr/jsr317/index.html">
-    public draft</ulink>.
-    </para>
-    </section>
-    
-    <section>
-    <title>Extension to Criteria API</title>
-    <para>
-    Criteria API has provided an alternative means to string-based JPQL to 
-    execute a query. However, JPA 2.0 Specification has not explicitly specified 
-    any equivalence between a dynamically constructed QueryDefinition and
-    a JPQL string. OpenJPA provides a mechanism to convert a QueryDefinition to
-    an equivalent JPQL query string via the extended OpenJPAQueryBuilder API.
-    <programlisting>
-    	public interface OpenJPAQueryBuilder extends QueryBuilder {
-			/**
-		 	 * Gets equivalent JPQL String for the given QueryDefinition.
-	 		*/
-			public String toJPQL(QueryDefinition qdef);
-		}
-	</programlisting>
-    
-    </para>
+    <para>
+    JPA 2.0 Specification introduces a new API to define queries dynamically
+    via construction of an object-based 
+    <classname>javax.persistence.QueryDefinition</classname> instance, rather
+    than string-based approach used in JPQL (Java Persistence Query Language).
+    This dynamic query definition capability, referred as Criteria API, is 
+    based on the abstract persistent schema of the entities, their embedded
+    objects and their relationships. The syntax is designed to construct a
+    <emphasis>Query Tree</emphasis> whose nodes represent the semantic query
+    elements such as projections, conditional predicates of WHERE clause or
+    GROUP BY elements etc. 
+    </para>
+    
+    <section>
+    	<title>Constructing a QueryDefinition</title>
+    	<para>
+    	The QueryBuilder interface is the factory for QueryDefinition. A
+    	QueryBuilder is obtained from either the EntityManagerFactory or 
+    	the EntityManager as follows:
+    	<programlisting>
+EntityManager em = ... ; 
+QueryBuilder queryBuilder = em.getQueryBuilder();
+QueryDefinition qdef = queryBuilder.createQueryDefinition();
+    	</programlisting>
+    	The first step in constructing a query definition is specification of 
+    	query roots.  Query roots specify the domain objects on which the query 
+    	is evaluated. Query root is an instance of the DomainObject interface. A
+    	query root is added to a QueryDefinition by 
+    	<methodname>addRoot(Class c)</methodname> method.
+    	<programlisting>
+    	DomainObject customer = qdef.addRoot(Customer.class);
+    	</programlisting>
+    	Often a query definition has a single root, so the 
+    	QueryBuilder interface allows to construct and add
+    	a root via a single method.
+    	<programlisting>
+DomainObject customer = queryBuilder.createQueryDefinition(Customer.class);    	
+    	</programlisting>
+    	A query domain can be further refined by joining to other domain objects.
+    	For example, for the above query definition to operate over customers 
+    	and their orders, use <methodname>join(String attribute)</methodname>:
+		<programlisting>
+DomainObject order = customer.join("orders");
+		</programlisting>  
+		The condition of a query definition is set via 
+		<methodname>where(Predicate p)</methodname> where the argument 
+		designates a conditional predicate. Conditional predicates are often
+		composed of one or more comparisons between the attribute values of
+		the domain objects and some variable. For example, to select the
+		Customers whose name is <emphasis>John Doe</emphasis> and has 
+		orders that are not yet delivered, you can build the predicate and set  
+		it to the query definition as
+		<programlisting>
+qdef.where(customer.get("name").equal("John Doe")
+      .and(order.get("status").equal(OrderStatus.DELIVERED).not()));
+		</programlisting>
+		The <methodname>select()</methodname> method defines the result of the
+		query. If left unspecified, the select projection is assumed to be the
+		root domain object. However, you can specify the selected projections
+		explicitly as a list 
+		<programlisting>
+qdef.select(customer.get("name"), order.get("status"));
+		</programlisting>
+		Attribute of a domain object is specified by navigating via 
+		<methodname>get(String attr)</methodname>. The attribute 
+		<emphasis>should</emphasis> refer
+		to a valid persistent property of the receiving domain object, however
+		no such validation is enforced during the construction of the query 
+		definition. All validation is deferred till query is actually executed.
+    	</para>
+    </section> 
+    
+    <section>
+    <title>Executing a QueryDefinition</title>
+    <para>
+    A QueryDefinition is executed in a similar fashion of a string-based JPQL
+    query via the EntityManager and Query interfaces.
+    <programlisting>
+EntityManager em = ...
+Query query = em.createQuery(qdef);
+List result = query.getResultList();    
+    </programlisting>
+    </para>
+    <para>
+    A query definition can use named parameters, and the parameter values are
+    set as usual in the Query instance. 
+    </para>
+    
+    <para>
+    The JPA 2.0 Specification on Criteria API is evolving and hence for an
+    up-to-date version of the API, please consult the  
+    <ulink url="http://jcp.org/aboutJava/communityprocess/pr/jsr317/index.html">
+    public draft</ulink>.
+    </para>
+    </section>
+    
+    <section>
+    <title>Extension to Criteria API</title>
+    <para>
+    Criteria API has provided an alternative means to string-based JPQL to 
+    execute a query. However, JPA 2.0 Specification has not explicitly specified 
+    any equivalence between a dynamically constructed QueryDefinition and
+    a JPQL string. OpenJPA provides a mechanism to convert a QueryDefinition to
+    an equivalent JPQL query string via the extended OpenJPAQueryBuilder API.
+    <programlisting>
+    	public interface OpenJPAQueryBuilder extends QueryBuilder {
+			/**
+		 	 * Gets equivalent JPQL String for the given QueryDefinition.
+	 		*/
+			public String toJPQL(QueryDefinition qdef);
+		}
+	</programlisting>
+    
+    </para>
     </section>
 
 </chapter>

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_em.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_emfactory.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_intro.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_mapping.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_meta.xml
------------------------------------------------------------------------------
    svn:eol-style = native

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=757388&r1=757387&r2=757388&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 Mon Mar 23 12:42:41 2009
@@ -65,12 +65,12 @@
 An instance of an embeddable class, on the other hand, is only stored as part of
 a separate entity. Embeddable instances have no persistent identity, and are
 never returned directly from the <classname>EntityManager</classname> or from a
-<classname>Query</classname> unless the query uses a projection on owning class 
-to the embedded instance. For example, if <classname>Address</classname> is 
-embedded in <classname>Company</classname>, then 
-a query <classname>"SELECT a FROM Address a"</classname> will never return the 
-embedded <classname>Address</classname> of <classname>Company</classname>; 
-but a projection query such as 
+<classname>Query</classname> unless the query uses a projection on owning class 
+to the embedded instance. For example, if <classname>Address</classname> is 
+embedded in <classname>Company</classname>, then 
+a query <classname>"SELECT a FROM Address a"</classname> will never return the 
+embedded <classname>Address</classname> of <classname>Company</classname>; 
+but a projection query such as 
 <classname>"SELECT c.address FROM Company c"</classname> will.
     </para>
     <para>

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_persistence.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_query.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_sqlquery.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_trans.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_why.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_resources.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/jpa_tutorials.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/manual.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: openjpa/trunk/openjpa-project/src/doc/manual/openjpa_intro.xml
------------------------------------------------------------------------------
    svn:eol-style = native

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=757388&r1=757387&r2=757388&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 Mon Mar 23 12:42:41 2009
@@ -395,8 +395,8 @@
 overflow eviction through the <methodname>unpin</methodname> methods. Use
 pinning when you want a guarantee that a certain object will always be available
 from cache, rather than requiring a datastore trip.
-            </para>
-            
+            </para>
+            
             
             <example id="ref_guide_cache_use_jpa">
                 <title>
@@ -442,74 +442,74 @@
 oem.evict(changedMag);  // will evict from data cache also
 </programlisting>
             </example>
-        </section>
-        
-        <section id="ref_guide_cache_statistics">
-        	<title>
-        		Cache Statistics
-        	</title>
-        	<indexterm>
-                <primary>
-                    caching
-                </primary>
-                <secondary>
-                    statistics
-                </secondary>
-        	</indexterm>
-        	
-        	<para>
-        	Number of requests to read and write requests and hit ratio of the 
-data cache is available via 
-<ulink url="../javadoc/org/apache/openjpa/datacache/CacheStatistics.html">
-<classname>org.apache.openjpa.datacache.CacheStatistics</classname></ulink> 
-interface. You can access this statistics via StoreCache 
-<programlisting>
-import org.apache.openjpa.datacache.CacheStatistics;
-...
-OpenJPAEntityManagerFactory oemf = OpenJPAPersistence.cast(emf);
-CacheStatistics statistics = oemf.getStoreCache().getCacheStatistics();
-</programlisting>
-The statistics includes number of read and write requests made to the cache 
-since start and last reset. The statistics can be obtained also per class basis.
-<programlisting>
-public interface org.apache.openjpa.datacache.CacheStatistics extends java.io.Serializable{
-    // Statistics since last reset
-    public long getReadCount();
-    public long getHitCount();
-    public long getWriteCount();
-    
-    // Statistics since start
-    public long getTotalReadCount();
-    public long getTotalHitCount();
-    public long getTotalWriteCount();
-    
-    // Per-Class statistics since last reset
-    public long getReadCount(java.lang.Class);
-    public long getHitCount(java.lang.Class);
-    public long getWriteCount(java.lang.Class);
-    
-    // Per-Class statistics since start
-    public long getTotalReadCount(java.lang.Class);
-    public long getTotalHitCount(java.lang.Class);
-    public long getTotalWriteCount(java.lang.Class);
-    
-    // Starting and last reset time 
-    public java.util.Date since();
-    public java.util.Date start();
-    
-    // Resets the statistics. 
-    public void reset();
-}
-</programlisting>
-Collecting per-class statistics depends on determining the runtime type of a
-cached data element, when the given context does not permit determination of
-exact runtime type, the statistics is registered against generic 
-<classname>java.lang.Object</classname>. Also each method that accepts Class 
-argument, treats null argument as <classname>java.lang.Object</classname>
-</para> 
-
         </section>
-        
+        
+        <section id="ref_guide_cache_statistics">
+        	<title>
+        		Cache Statistics
+        	</title>
+        	<indexterm>
+                <primary>
+                    caching
+                </primary>
+                <secondary>
+                    statistics
+                </secondary>
+        	</indexterm>
+        	
+        	<para>
+        	Number of requests to read and write requests and hit ratio of the 
+data cache is available via 
+<ulink url="../javadoc/org/apache/openjpa/datacache/CacheStatistics.html">
+<classname>org.apache.openjpa.datacache.CacheStatistics</classname></ulink> 
+interface. You can access this statistics via StoreCache 
+<programlisting>
+import org.apache.openjpa.datacache.CacheStatistics;
+...
+OpenJPAEntityManagerFactory oemf = OpenJPAPersistence.cast(emf);
+CacheStatistics statistics = oemf.getStoreCache().getCacheStatistics();
+</programlisting>
+The statistics includes number of read and write requests made to the cache 
+since start and last reset. The statistics can be obtained also per class basis.
+<programlisting>
+public interface org.apache.openjpa.datacache.CacheStatistics extends java.io.Serializable{
+    // Statistics since last reset
+    public long getReadCount();
+    public long getHitCount();
+    public long getWriteCount();
+    
+    // Statistics since start
+    public long getTotalReadCount();
+    public long getTotalHitCount();
+    public long getTotalWriteCount();
+    
+    // Per-Class statistics since last reset
+    public long getReadCount(java.lang.Class);
+    public long getHitCount(java.lang.Class);
+    public long getWriteCount(java.lang.Class);
+    
+    // Per-Class statistics since start
+    public long getTotalReadCount(java.lang.Class);
+    public long getTotalHitCount(java.lang.Class);
+    public long getTotalWriteCount(java.lang.Class);
+    
+    // Starting and last reset time 
+    public java.util.Date since();
+    public java.util.Date start();
+    
+    // Resets the statistics. 
+    public void reset();
+}
+</programlisting>
+Collecting per-class statistics depends on determining the runtime type of a
+cached data element, when the given context does not permit determination of
+exact runtime type, the statistics is registered against generic 
+<classname>java.lang.Object</classname>. Also each method that accepts Class 
+argument, treats null argument as <classname>java.lang.Object</classname>
+</para> 
+
+        </section>
+        
         <section id="ref_guide_cache_query">
             <title>
                 Query Cache
@@ -1022,7 +1022,7 @@
 				</tbody>
 			</tgroup>
 		</table>
-	</section>
+	</section>
 	
     <section id="ref_guide_cache_querysql">
         <title>Prepared SQL Cache</title>
@@ -1030,147 +1030,147 @@
             <primary>caching</primary>
             <secondary>query sql cache</secondary>
         </indexterm>
-         <para>
-Prepared SQL Cache caches SQL statements corresponding to JPQL queries.
-If a JPQL query is executed more than once in the same or different persistence
-contexts, the SQL statement generated during the first execution is cached and
-executed directly for subsequent execution. Direct execution of SQL offers
-significant performance gain as it saves the cost of parsing query string and,
-more importantly, populating the query expression tree during every execution.
-Relative performance gain becomes higher as the complexity of forming a SQL 
-query from a JPQL string increases. For example, a JPQL query <code>Q1</code>
-that involves multiple joins across tables takes more computation to translate 
-into a SQL statement than a JPQL query <code>Q2</code> to select by simple 
-primary key identifier. Correspondingly, repeated execution of <code>Q1</code>
-will gain more performance advantage than <code>Q2</code> with Prepared SQL
-Cache. 
-</para>
-<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"/>)
-with value of <literal>true</literal> or <literal>false</literal>. The default
-is <literal>true</literal>. 
-</para>
-<para>
-Following salient points to be noted regarding usage of Prepared Query Cache.
-<itemizedlist>
-	<listitem>
-	<para>
-	Prepared Query Cache uses the original JPQL string as the key to index the 
-	corresponding SQL statement. Hence the JPQL strings that are semantically 
-	identical but differ by character case or identification variables are 
-	considered as different by this cache. One of the implications is that the 
-	applications can gain better advantage from the Prepared Query Cache by
-	using parameters in their JPQL query rather than concatenating the parameter 
-	values in the query string itself . 
-	</para>
-	<para>
-	For example, contrast the following two examples of executing JPQL queries.
-	<example id="jpa_caching_hardcode_jpql"> 
-	   <title>Hardcoded Selection Value in JPQL Query</title> 
-	<programlisting>
-	String jpql = "SELECT p FROM Person p WHERE p.name='John'";
-	List johns = em.createQuery(jpql).getResultList();
-	jpql = "SELECT p FROM Person p WHERE p.name='Tom'";
-	List toms = em.createQuery(jpql).getResultList();
-	</programlisting>
-	</example>
-	In <xref linkend="jpa_caching_hardcode_jpql"></xref>, the queries have 
-	<emphasis>hardcoded</emphasis> the	selection value for the <code>p.name</code> 
-	field. Prepared Query Cache will not recognize the second execution as
-	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 
-	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. 
-	
-	<example id="jpa_caching_parametrize_jpql"> 
-	   <title>Parameterized Selection Value in JPQL Query</title> 
-	<programlisting>
-	String jpql = "SELECT p FROM Person p WHERE p.name=:name";
-	List johns = em.createQuery(jpql).setParameter("name","John").getResultList();
-	List toms = em.createQuery(jpql).setParameter("name","John").getResultList();
-	</programlisting>
-	</example>
-	</para>
-	</listitem>
-	
-	<listitem>
-    A JPQL query may not always translate into a <emphasis>single</emphasis> 
-    SQL query. The JPQL queries that require multiple select statements are 
-    never cached. 
-    </listitem>
-	<listitem>
-	Same JPQL query may result into different SQL statements under different
-	execution context. Execution context parameters such as fetch configuration 
-	or locking mode determine the resultant SQL. However, Prepared SQL Cache
-	<emphasis>does not</emphasis> capture the execution context parameters
-	while caching a generated SQL.  
-	</listitem>
-	<listitem>
-	The named or positional parameters of a JPQL query can be set to different
-	values across executions. In general, the corresponding cached SQL statement 
-	will be re-parameterized accordingly. However, the parameter value itself can 
-	determine the SQL query. For example, when a JPQL query compares a relation 
-	field for equality against a parameter <code>p</code>, whether the actual
-	value of <code>p</code> is <code>null</code> or not will determine the
-	generated SQL statement. Another example is collection valued parameter for
-	<code>IN</code> expression. Each element of a collection valued parameter 
-	results into a SQL parameter. If a collection valued parameter across
-	executions are set to different number of elements, then the parameters of
-	the cached SQL do not correspond. If such situations are encountered while 
-	re-parameterizing the cached SQL, the cached version is not reused and the
-	original JPQL query is used to generate a new SQL statement for execution. 
-	</listitem>
-	<listitem>
-	JPQL query that returns a <emphasis>numeric</emphasis> value such as 
-	<code>SELECT count(p) FROM PObject p</code> is never cached.
-	</listitem>
-</itemizedlist>
-</para>
-<para>
-Several mechanisms are available to the application to bypass SQL caching
-for a JPQL query. 
-<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:
-	<programlisting>
-	<methodname>OpenJPAEntityManager.setQuerySQLCache(boolean)</methodname> 
-	</programlisting>
-	</listitem>
-	<listitem>
-	A user application can instruct particular execution of a JPQL query to
-	ignore any cached SQL query, by setting 
-	<literal>QueryHints.HINT_IGNORE_PREPARED_QUERY</literal> or 
-	<literal>"openjpa.hint.IgnorePreparedQuery"</literal> to <literal>true</literal>
-	via standard <literal>javax.persistence.Query.setHint(String, Object)</literal> method. If a
-	SQL query has been cached corresponding to the JPQL query prior to this 
-	execution, then the cached SQL remains in the cache and will be reused
-	for any subsequent execution of the same JPQL query.
-	</listitem>
-	<listitem>
-	A user application can instruct all subsequent execution of a JPQL query to
-	ignore any cached SQL query, by setting 
-	<literal>QueryHints.HINT_INVALIDATE_PREPARED_QUERY</literal> or 
-	<literal>"openjpa.hint.InvalidatePreparedQuery"</literal> to <literal>true</literal>
-	The SQL query is removed from the cache. Also the JPQL query will never be
-	cached again during the lifetime of the entire persistence unit.
-	</listitem>
-	<listitem>
-	Plug-in property <literal>openjpa.jdbc.QuerySQLCache</literal> can be 
-	configured to exclude certain JPQL queries as shown below.
-	<programlisting>
-	&lt;property name="openjpa.jdbc.QuerySQLCache" value="true(excludes='select c from Company c;select d from Department d')"/&gt;
-	</programlisting> 
-	will never cache JPQL queries <code>select c from Company c</code> and 
-	<code>select d from Department d</code>.
-	</listitem>
-	</itemizedlist>
-</para>
+         <para>
+Prepared SQL Cache caches SQL statements corresponding to JPQL queries.
+If a JPQL query is executed more than once in the same or different persistence
+contexts, the SQL statement generated during the first execution is cached and
+executed directly for subsequent execution. Direct execution of SQL offers
+significant performance gain as it saves the cost of parsing query string and,
+more importantly, populating the query expression tree during every execution.
+Relative performance gain becomes higher as the complexity of forming a SQL 
+query from a JPQL string increases. For example, a JPQL query <code>Q1</code>
+that involves multiple joins across tables takes more computation to translate 
+into a SQL statement than a JPQL query <code>Q2</code> to select by simple 
+primary key identifier. Correspondingly, repeated execution of <code>Q1</code>
+will gain more performance advantage than <code>Q2</code> with Prepared SQL
+Cache. 
+</para>
+<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"/>)
+with value of <literal>true</literal> or <literal>false</literal>. The default
+is <literal>true</literal>. 
+</para>
+<para>
+Following salient points to be noted regarding usage of Prepared Query Cache.
+<itemizedlist>
+	<listitem>
+	<para>
+	Prepared Query Cache uses the original JPQL string as the key to index the 
+	corresponding SQL statement. Hence the JPQL strings that are semantically 
+	identical but differ by character case or identification variables are 
+	considered as different by this cache. One of the implications is that the 
+	applications can gain better advantage from the Prepared Query Cache by
+	using parameters in their JPQL query rather than concatenating the parameter 
+	values in the query string itself . 
+	</para>
+	<para>
+	For example, contrast the following two examples of executing JPQL queries.
+	<example id="jpa_caching_hardcode_jpql"> 
+	   <title>Hardcoded Selection Value in JPQL Query</title> 
+	<programlisting>
+	String jpql = "SELECT p FROM Person p WHERE p.name='John'";
+	List johns = em.createQuery(jpql).getResultList();
+	jpql = "SELECT p FROM Person p WHERE p.name='Tom'";
+	List toms = em.createQuery(jpql).getResultList();
+	</programlisting>
+	</example>
+	In <xref linkend="jpa_caching_hardcode_jpql"></xref>, the queries have 
+	<emphasis>hardcoded</emphasis> the	selection value for the <code>p.name</code> 
+	field. Prepared Query Cache will not recognize the second execution as
+	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 
+	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. 
+	
+	<example id="jpa_caching_parametrize_jpql"> 
+	   <title>Parameterized Selection Value in JPQL Query</title> 
+	<programlisting>
+	String jpql = "SELECT p FROM Person p WHERE p.name=:name";
+	List johns = em.createQuery(jpql).setParameter("name","John").getResultList();
+	List toms = em.createQuery(jpql).setParameter("name","John").getResultList();
+	</programlisting>
+	</example>
+	</para>
+	</listitem>
+	
+	<listitem>
+    A JPQL query may not always translate into a <emphasis>single</emphasis> 
+    SQL query. The JPQL queries that require multiple select statements are 
+    never cached. 
+    </listitem>
+	<listitem>
+	Same JPQL query may result into different SQL statements under different
+	execution context. Execution context parameters such as fetch configuration 
+	or locking mode determine the resultant SQL. However, Prepared SQL Cache
+	<emphasis>does not</emphasis> capture the execution context parameters
+	while caching a generated SQL.  
+	</listitem>
+	<listitem>
+	The named or positional parameters of a JPQL query can be set to different
+	values across executions. In general, the corresponding cached SQL statement 
+	will be re-parameterized accordingly. However, the parameter value itself can 
+	determine the SQL query. For example, when a JPQL query compares a relation 
+	field for equality against a parameter <code>p</code>, whether the actual
+	value of <code>p</code> is <code>null</code> or not will determine the
+	generated SQL statement. Another example is collection valued parameter for
+	<code>IN</code> expression. Each element of a collection valued parameter 
+	results into a SQL parameter. If a collection valued parameter across
+	executions are set to different number of elements, then the parameters of
+	the cached SQL do not correspond. If such situations are encountered while 
+	re-parameterizing the cached SQL, the cached version is not reused and the
+	original JPQL query is used to generate a new SQL statement for execution. 
+	</listitem>
+	<listitem>
+	JPQL query that returns a <emphasis>numeric</emphasis> value such as 
+	<code>SELECT count(p) FROM PObject p</code> is never cached.
+	</listitem>
+</itemizedlist>
+</para>
+<para>
+Several mechanisms are available to the application to bypass SQL caching
+for a JPQL query. 
+<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:
+	<programlisting>
+	<methodname>OpenJPAEntityManager.setQuerySQLCache(boolean)</methodname> 
+	</programlisting>
+	</listitem>
+	<listitem>
+	A user application can instruct particular execution of a JPQL query to
+	ignore any cached SQL query, by setting 
+	<literal>QueryHints.HINT_IGNORE_PREPARED_QUERY</literal> or 
+	<literal>"openjpa.hint.IgnorePreparedQuery"</literal> to <literal>true</literal>
+	via standard <literal>javax.persistence.Query.setHint(String, Object)</literal> method. If a
+	SQL query has been cached corresponding to the JPQL query prior to this 
+	execution, then the cached SQL remains in the cache and will be reused
+	for any subsequent execution of the same JPQL query.
+	</listitem>
+	<listitem>
+	A user application can instruct all subsequent execution of a JPQL query to
+	ignore any cached SQL query, by setting 
+	<literal>QueryHints.HINT_INVALIDATE_PREPARED_QUERY</literal> or 
+	<literal>"openjpa.hint.InvalidatePreparedQuery"</literal> to <literal>true</literal>
+	The SQL query is removed from the cache. Also the JPQL query will never be
+	cached again during the lifetime of the entire persistence unit.
+	</listitem>
+	<listitem>
+	Plug-in property <literal>openjpa.jdbc.QuerySQLCache</literal> can be 
+	configured to exclude certain JPQL queries as shown below.
+	<programlisting>
+	&lt;property name="openjpa.jdbc.QuerySQLCache" value="true(excludes='select c from Company c;select d from Department d')"/&gt;
+	</programlisting> 
+	will never cache JPQL queries <code>select c from Company c</code> and 
+	<code>select d from Department d</code>.
+	</listitem>
+	</itemizedlist>
+</para>
  
     </section>
 </chapter>

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=757388&r1=757387&r2=757388&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 23 12:42:41 2009
@@ -359,7 +359,7 @@
         </para>
 <programlisting>
 true(CacheSize=1000)
-</programlisting>
+</programlisting>
 
         <para>
 The remainder of this chapter reviews the set of configuration properties
@@ -384,51 +384,51 @@
 majority of developers can omit them. The following properties apply to any
 OpenJPA back-end, though the given descriptions are tailored to OpenJPA's
 default JDBC store.
-        </para>
-        
-        <para>
-Few of the properties recognized by OpenJPA have been standardized in JPA 2.0 
-Specification using equivalent names. These properties can be specified either
-by the JPA standard key or equivalent OpenJPA key. Specifying the same key once
-as JPA standard key and again as equivalent OpenJPA key in the same configuration, 
-however, is not allowed. The following table lists these standard JPA properties 
-and their OpenJPA equivalent.
-        </para>
-    <table tocentry="1">
-        <title>
-            Standard JPA Properties and OpenJPA equivalents
-        </title>
-        <tgroup rowsep="1" colsep="8" align="left" cols="2">
-            <colspec colname="StandardJPA"/>
-            <colspec colname="OpenJPAEquivalent"/>
-            <thead>
-                <row>
-                    <entry colname="StandardJPA">Standard JPA 2.0</entry>
-                    <entry colname="OpenJPAEquivalent">OpenJPA Equivalent</entry>
-                </row>
-            </thead>
-            <tbody>
-                <row>
-                    <entry colname="StandardJPA">javax.persistence.jdbc.driver</entry>
-                    <entry colname="OpenJPAEquivalent">openjpa.ConnectionDriverName</entry>
-                </row>
-                <row>
-                    <entry colname="StandardJPA">javax.persistence.jdbc.url</entry>
-                    <entry colname="OpenJPAEquivalent">openjpa.ConnectionURL</entry>
-                </row>
-                <row>
-                    <entry colname="StandardJPA">javax.persistence.jdbc.user</entry>
-                    <entry colname="OpenJPAEquivalent">openjpa.ConnectionUserName</entry>
-                </row>
-                <row>
-                    <entry colname="StandardJPA">javax.persistence.jdbc.password</entry>
-                    <entry colname="OpenJPAEquivalent">openjpa.ConnectionPassword</entry>
-                </row>
-           </tbody>
-        </tgroup>
-    </table>
-        
-        
+        </para>
+        
+        <para>
+Few of the properties recognized by OpenJPA have been standardized in JPA 2.0 
+Specification using equivalent names. These properties can be specified either
+by the JPA standard key or equivalent OpenJPA key. Specifying the same key once
+as JPA standard key and again as equivalent OpenJPA key in the same configuration, 
+however, is not allowed. The following table lists these standard JPA properties 
+and their OpenJPA equivalent.
+        </para>
+    <table tocentry="1">
+        <title>
+            Standard JPA Properties and OpenJPA equivalents
+        </title>
+        <tgroup rowsep="1" colsep="8" align="left" cols="2">
+            <colspec colname="StandardJPA"/>
+            <colspec colname="OpenJPAEquivalent"/>
+            <thead>
+                <row>
+                    <entry colname="StandardJPA">Standard JPA 2.0</entry>
+                    <entry colname="OpenJPAEquivalent">OpenJPA Equivalent</entry>
+                </row>
+            </thead>
+            <tbody>
+                <row>
+                    <entry colname="StandardJPA">javax.persistence.jdbc.driver</entry>
+                    <entry colname="OpenJPAEquivalent">openjpa.ConnectionDriverName</entry>
+                </row>
+                <row>
+                    <entry colname="StandardJPA">javax.persistence.jdbc.url</entry>
+                    <entry colname="OpenJPAEquivalent">openjpa.ConnectionURL</entry>
+                </row>
+                <row>
+                    <entry colname="StandardJPA">javax.persistence.jdbc.user</entry>
+                    <entry colname="OpenJPAEquivalent">openjpa.ConnectionUserName</entry>
+                </row>
+                <row>
+                    <entry colname="StandardJPA">javax.persistence.jdbc.password</entry>
+                    <entry colname="OpenJPAEquivalent">openjpa.ConnectionPassword</entry>
+                </row>
+           </tbody>
+        </tgroup>
+    </table>
+        
+        
         
         <!--
         <section id="openjpa.AggregateListeners">
@@ -649,53 +649,53 @@
 <xref linkend="ref_guide_runtime_broker_extension"/> on for details.
             </para>
         </section>
-
-<section id="openjpa.Callbacks">
-            <title>openjpa.Callbacks</title>
-            <indexterm zone="openjpa.Callbacks">
-                <primary>Callbacks</primary>
-            </indexterm>
-            <indexterm>
-                <primary>Callbacks</primary>
-                <see>Callbacks</see>
-            </indexterm>
-  <para>
-     <emphasis role="bold">Property name: </emphasis><literal>openjpa.Callbacks</literal>
-  </para>
-  <para>
-     <emphasis role="bold">Configuration API:</emphasis>
-     <ulink url="../javadoc/org/apache/openjpa/conf/OpenJPAConfiguration.html#getCallbackOptionsInstance()">
-     <methodname>org.apache.openjpa.conf.OpenJPAConfiguration.getCallbackOptionsInstance</methodname></ulink>
-  </para>
-  <para>
-     <emphasis role="bold">Resource adaptor config-property: </emphasis><literal>Callbacks</literal>
-  </para>
-  <para>
-     <emphasis role="bold">Default: </emphasis><literal>default</literal>
-  </para>
-  <para>
-     <emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"/>) to fine tune some of the configurable
-properties related to callbacks. The plug-in supports two boolean properties:
-   </para>
-   <itemizedlist>
-   	<listitem>
-   		<para><literal>PostPersistCallbackImmediate</literal>: whether the 
-   		post-persist callback is invoked as soon as a new instance
-        is managed. The default is <literal>false</literal>, implies that 
-        the post-persist callback is invoked after the instance been committed 
-        or flushed to the datastore.
-        </para>
-   	</listitem>
-   	<listitem>
-   	    <para><literal>AllowsMultipleMethodsForSameCallback</literal>: whether
-   	    multiple methods of the same class can handle the same callback event.
-   	    Defaults to <literal>false</literal>.
-   	    </para>
-   	</listitem>
-   </itemizedlist>
-</section>
-
+
+<section id="openjpa.Callbacks">
+            <title>openjpa.Callbacks</title>
+            <indexterm zone="openjpa.Callbacks">
+                <primary>Callbacks</primary>
+            </indexterm>
+            <indexterm>
+                <primary>Callbacks</primary>
+                <see>Callbacks</see>
+            </indexterm>
+  <para>
+     <emphasis role="bold">Property name: </emphasis><literal>openjpa.Callbacks</literal>
+  </para>
+  <para>
+     <emphasis role="bold">Configuration API:</emphasis>
+     <ulink url="../javadoc/org/apache/openjpa/conf/OpenJPAConfiguration.html#getCallbackOptionsInstance()">
+     <methodname>org.apache.openjpa.conf.OpenJPAConfiguration.getCallbackOptionsInstance</methodname></ulink>
+  </para>
+  <para>
+     <emphasis role="bold">Resource adaptor config-property: </emphasis><literal>Callbacks</literal>
+  </para>
+  <para>
+     <emphasis role="bold">Default: </emphasis><literal>default</literal>
+  </para>
+  <para>
+     <emphasis role="bold">Description:</emphasis> A plugin string (see
+<xref linkend="ref_guide_conf_plugins"/>) to fine tune some of the configurable
+properties related to callbacks. The plug-in supports two boolean properties:
+   </para>
+   <itemizedlist>
+   	<listitem>
+   		<para><literal>PostPersistCallbackImmediate</literal>: whether the 
+   		post-persist callback is invoked as soon as a new instance
+        is managed. The default is <literal>false</literal>, implies that 
+        the post-persist callback is invoked after the instance been committed 
+        or flushed to the datastore.
+        </para>
+   	</listitem>
+   	<listitem>
+   	    <para><literal>AllowsMultipleMethodsForSameCallback</literal>: whether
+   	    multiple methods of the same class can handle the same callback event.
+   	    Defaults to <literal>false</literal>.
+   	    </para>
+   	</listitem>
+   </itemizedlist>
+</section>
+
         <section id="openjpa.ClassResolver">
             <title>
                 openjpa.ClassResolver
@@ -1983,59 +1983,59 @@
             might correspond to a JPA persistence-unit name, or to some other
             more-unique value available in the current environment.
             </para>
-        </section>
-        
-InitializeEagerly
-        <section id="openjpa.InitializeEagerly">
-            <title>
-                openjpa.InitializeEagerly
-            </title>
-            <indexterm zone="openjpa.InitializeEagerly">
-                <primary>
-                    InverseManager
-                </primary>
-            </indexterm>
-            <indexterm zone="openjpa.InitializeEagerly">
-                <primary>
-                    Initialization
-                </primary>
-                <secondary>
-                    Configuration
-                </secondary>
-            </indexterm>
-            <para>
-<emphasis role="bold">Property name: </emphasis><literal>openjpa.InitializeEagerly
-</literal>
-            </para>
-            <para>
-<emphasis role="bold">Configuration API:</emphasis>
-<ulink url="../javadoc/org/apache/openjpa/conf/OpenJPAConfiguration.html#isInitializeEagerly()">
-<methodname>org.apache.openjpa.conf.OpenJPAConfiguration.isInitializeEagerly
-</methodname></ulink>
-            </para>
-            <para>
-<emphasis role="bold">Resource adaptor config-property: </emphasis><literal>
-InitializeEagerly</literal>
-            </para>
-            <para>
-<emphasis role="bold">Default: </emphasis><literal>false</literal>
-            </para>
-            <para>
-<emphasis role="bold">Possible values: </emphasis><literal>false</literal>,
-<literal>true</literal>
-            </para>
-            <para>
-<emphasis role="bold">Description:</emphasis> Controls whether initialization
-is eager or lazy. Eager initialization imply all persistent classes, their 
-mapping information, database connectivity and all other resources specified in
-the configuration of a persistence unit will be initialized when a persistent 
-unit is constructed. The default behavior is
-lazy i.e. persistent classes, database and other resources are initialized only
-when the application refers to a resource for the first time.
-            </para>
-        </section>
-
-
+        </section>
+        
+InitializeEagerly
+        <section id="openjpa.InitializeEagerly">
+            <title>
+                openjpa.InitializeEagerly
+            </title>
+            <indexterm zone="openjpa.InitializeEagerly">
+                <primary>
+                    InverseManager
+                </primary>
+            </indexterm>
+            <indexterm zone="openjpa.InitializeEagerly">
+                <primary>
+                    Initialization
+                </primary>
+                <secondary>
+                    Configuration
+                </secondary>
+            </indexterm>
+            <para>
+<emphasis role="bold">Property name: </emphasis><literal>openjpa.InitializeEagerly
+</literal>
+            </para>
+            <para>
+<emphasis role="bold">Configuration API:</emphasis>
+<ulink url="../javadoc/org/apache/openjpa/conf/OpenJPAConfiguration.html#isInitializeEagerly()">
+<methodname>org.apache.openjpa.conf.OpenJPAConfiguration.isInitializeEagerly
+</methodname></ulink>
+            </para>
+            <para>
+<emphasis role="bold">Resource adaptor config-property: </emphasis><literal>
+InitializeEagerly</literal>
+            </para>
+            <para>
+<emphasis role="bold">Default: </emphasis><literal>false</literal>
+            </para>
+            <para>
+<emphasis role="bold">Possible values: </emphasis><literal>false</literal>,
+<literal>true</literal>
+            </para>
+            <para>
+<emphasis role="bold">Description:</emphasis> Controls whether initialization
+is eager or lazy. Eager initialization imply all persistent classes, their 
+mapping information, database connectivity and all other resources specified in
+the configuration of a persistence unit will be initialized when a persistent 
+unit is constructed. The default behavior is
+lazy i.e. persistent classes, database and other resources are initialized only
+when the application refers to a resource for the first time.
+            </para>
+        </section>
+
+
         
         <section id="openjpa.InverseManager">
             <title>
@@ -3016,43 +3016,43 @@
 system sequence. See <xref linkend="ref_guide_sequence"/> for more
 information.
             </para>
-        </section>
-        <section id="openjpa.Specification">
-            <title>
-                openjpa.Specification
-            </title>
-            <indexterm zone="openjpa.Specification">
-                <primary>
-                    Specification
-                </primary>
-            </indexterm>
-            <para>
-<emphasis role="bold">Property name: </emphasis><literal>openjpa.Specification
-</literal>
-            </para>
-            <para>
-<emphasis role="bold">Configuration API:</emphasis>
-<ulink url="../javadoc/org/apache/openjpa/conf/OpenJPAConfiguration.html#getSpecificationInstance()">
-<methodname>org.apache.openjpa.conf.OpenJPAConfiguration.getSpecificationInstance
-</methodname></ulink>
-            </para>
-            <para>
-<emphasis role="bold">Resource adaptor config-property: </emphasis><literal>
-Specification</literal>
-            </para>
-            <para>
-<emphasis role="bold">Default: </emphasis><literal>table</literal>
-            </para>
-            <para>
-<emphasis role="bold">Description:</emphasis> A formatted string describing the Specification
-to use for the default configuration options. The format of the Specifcation string is 
-<literal>name [major.[minor]]</literal> where <literal>name</literal> denotes the name of the
-Specification such as <literal>JPA</literal> or <literal>JDO</literal>, <literal>major</literal>
-denotes the major integral version number of the Specification and <literal>minor</literal>
-denotes a minor version which can be an arbitrary string.  
-See <xref linkend="ref_guide_spec_compatibility"/> for more information.
-            </para>
-        </section>
+        </section>
+        <section id="openjpa.Specification">
+            <title>
+                openjpa.Specification
+            </title>
+            <indexterm zone="openjpa.Specification">
+                <primary>
+                    Specification
+                </primary>
+            </indexterm>
+            <para>
+<emphasis role="bold">Property name: </emphasis><literal>openjpa.Specification
+</literal>
+            </para>
+            <para>
+<emphasis role="bold">Configuration API:</emphasis>
+<ulink url="../javadoc/org/apache/openjpa/conf/OpenJPAConfiguration.html#getSpecificationInstance()">
+<methodname>org.apache.openjpa.conf.OpenJPAConfiguration.getSpecificationInstance
+</methodname></ulink>
+            </para>
+            <para>
+<emphasis role="bold">Resource adaptor config-property: </emphasis><literal>
+Specification</literal>
+            </para>
+            <para>
+<emphasis role="bold">Default: </emphasis><literal>table</literal>
+            </para>
+            <para>
+<emphasis role="bold">Description:</emphasis> A formatted string describing the Specification
+to use for the default configuration options. The format of the Specifcation string is 
+<literal>name [major.[minor]]</literal> where <literal>name</literal> denotes the name of the
+Specification such as <literal>JPA</literal> or <literal>JDO</literal>, <literal>major</literal>
+denotes the major integral version number of the Specification and <literal>minor</literal>
+denotes a minor version which can be an arbitrary string.  
+See <xref linkend="ref_guide_spec_compatibility"/> for more information.
+            </para>
+        </section>
         
         <section id="openjpa.TransactionMode">
             <title>
@@ -3565,7 +3565,7 @@
 <classname>org.apache.openjpa.meta.MetaDataFactory</classname></ulink> to use to
 store and retrieve object-relational mapping information for your persistent
 classes. See <xref linkend="ref_guide_mapping_factory"/> for details.
-            </para>
+            </para>
             
         </section>
         <section id="openjpa.jdbc.QuerySQLCache">
@@ -3598,8 +3598,8 @@
             </para>
             <para>
 <emphasis role="bold">Description:</emphasis> A plugin string (see 
-<xref linkend="ref_guide_conf_plugins"/>) describing the options to cache and 
-reuse SQL statements generated for JPQL queries. 
+<xref linkend="ref_guide_conf_plugins"/>) describing the options to cache and 
+reuse SQL statements generated for JPQL queries. 
 See <xref linkend="ref_guide_cache_querysql"/> for details.
             </para>
         </section>
@@ -4005,44 +4005,44 @@
 <classname>org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager</classname>
 </ulink>.
 
-            </para>
-        </section>
-        
-        <section id="ref_guide_spec_compatibility">
-        <title>Compatibility with Specification</title>
-        <para>
-The default behavior of certain OpenJPA API methods can evolve to align with the behaviors
-defined in JPA specification. To maintain backward compatibility, OpenJPA allows configuration
-options such that while the default behavior changes to align with current JPA Specification, the
-previous behaviors can always be emulated. 
-		</para>
-		<para>
-For example, JPA 2.0 specification
-introduces a new API <literal>void EntityManager.detach(Object entity)</literal> that detaches
-the given entity from the current persistence context. OpenJPA has provided similar
-feature via <literal>&lt;T&gt; T OpenJPAEntityManager.detach(T entity)</literal> prior to JPA 2.0. 
-OpenJPA <literal>detach()</literal>, however, has different default behavior than what JPA 2.0
-specification mandates. Firstly, OpenJPA creates a copy of the given entity as a detached instance
-and returns it, whereas JPA 2.0 behavior requires the same given entity instance be detached.
-Secondly, the given instance is removed from the persistence context for JPA 2.0, whereas
-OpenJPA <literal>detach()</literal> method, prior to JPA 2.0, does not remove the instance
-from the persistence context as a copy is returned. Thirdly, OpenJPA will flush before
-detaching a dirty instance so that the detached instance can later be merged, whereas
-JPA 2.0 <literal>detach()</literal> semantics does not require a dirty instance be flushed
-before detach.        
-		</para>
-		<para>
-A user application running with OpenJPA that is compliant to a specific version of JPA of specification,
-the older behavior can be emulated by configuring OpenJPA Compatibility options.
-For example, <literal>openjpa.Compatibility=FlushBeforeDetach=false,CopyOnDetach=true</literal>
-will emulate the older behavior of detach even when running with OpenJPA that are
-compliant to JPA 2.0 Specification.  The configuration can also be set to a different version of the specification.
-For example, <literal>openjpa.Specification="JPA 1.0"</literal> configuration setting will emulate
-default OpenJPA behavior as it were for JPA Specification version 1.0. Setting via
-<literal>openjpa.Specification</literal> is a shorthand for more fine-grained control available via
-<literal>openjpa.Compatibility</literal>.    
-  
-		</para>
-        </section>
+            </para>
+        </section>
+        
+        <section id="ref_guide_spec_compatibility">
+        <title>Compatibility with Specification</title>
+        <para>
+The default behavior of certain OpenJPA API methods can evolve to align with the behaviors
+defined in JPA specification. To maintain backward compatibility, OpenJPA allows configuration
+options such that while the default behavior changes to align with current JPA Specification, the
+previous behaviors can always be emulated. 
+		</para>
+		<para>
+For example, JPA 2.0 specification
+introduces a new API <literal>void EntityManager.detach(Object entity)</literal> that detaches
+the given entity from the current persistence context. OpenJPA has provided similar
+feature via <literal>&lt;T&gt; T OpenJPAEntityManager.detach(T entity)</literal> prior to JPA 2.0. 
+OpenJPA <literal>detach()</literal>, however, has different default behavior than what JPA 2.0
+specification mandates. Firstly, OpenJPA creates a copy of the given entity as a detached instance
+and returns it, whereas JPA 2.0 behavior requires the same given entity instance be detached.
+Secondly, the given instance is removed from the persistence context for JPA 2.0, whereas
+OpenJPA <literal>detach()</literal> method, prior to JPA 2.0, does not remove the instance
+from the persistence context as a copy is returned. Thirdly, OpenJPA will flush before
+detaching a dirty instance so that the detached instance can later be merged, whereas
+JPA 2.0 <literal>detach()</literal> semantics does not require a dirty instance be flushed
+before detach.        
+		</para>
+		<para>
+A user application running with OpenJPA that is compliant to a specific version of JPA of specification,
+the older behavior can be emulated by configuring OpenJPA Compatibility options.
+For example, <literal>openjpa.Compatibility=FlushBeforeDetach=false,CopyOnDetach=true</literal>
+will emulate the older behavior of detach even when running with OpenJPA that are
+compliant to JPA 2.0 Specification.  The configuration can also be set to a different version of the specification.
+For example, <literal>openjpa.Specification="JPA 1.0"</literal> configuration setting will emulate
+default OpenJPA behavior as it were for JPA Specification version 1.0. Setting via
+<literal>openjpa.Specification</literal> is a shorthand for more fine-grained control available via
+<literal>openjpa.Compatibility</literal>.    
+  
+		</para>
+        </section>
     </section>
 </chapter>



Mime
View raw message