diff --git a/openjpa-project/src/doc/manual/jpa_overview_arch.xml b/openjpa-project/src/doc/manual/jpa_overview_arch.xml
index 0cf3f3632..ec10f1947 100644
--- a/openjpa-project/src/doc/manual/jpa_overview_arch.xml
+++ b/openjpa-project/src/doc/manual/jpa_overview_arch.xml
@@ -299,7 +299,7 @@ appropriate, most notably IllegalArgumentExceptions and
IllegalStateExceptions. The specification also provides
a few JPA-specific exceptions in the javax.persistence
package. These exceptions should be self-explanatory. See the
-Javadoc for
+Javadoc for
additional details on JPA exceptions.
diff --git a/openjpa-project/src/doc/manual/jpa_overview_em.xml b/openjpa-project/src/doc/manual/jpa_overview_em.xml
index 9db822941..a207b9bfb 100644
--- a/openjpa-project/src/doc/manual/jpa_overview_em.xml
+++ b/openjpa-project/src/doc/manual/jpa_overview_em.xml
@@ -37,7 +37,7 @@
The diagram above presents an overview of the EntityManager
interface. For a complete treatment of the
EntityManager API, see the
-
+
Javadoc documentation. Methods whose parameter signatures consist of
an ellipsis (...) are overloaded to take multiple parameter types.
@@ -515,7 +515,7 @@ public void lock(Object entity, LockModeType mode);
This method locks the given entity using the named mode. The
-
+
javax.persistence.LockModeType enum defines two
modes:
@@ -916,7 +916,7 @@ The EntityManager's FlushMode property
controls whether to flush transactional changes before executing queries. This
allows the query results to take into account changes you have made during the
current transaction. Available
-
+
javax.persistence.FlushModeType constants are:
diff --git a/openjpa-project/src/doc/manual/jpa_overview_pc.xml b/openjpa-project/src/doc/manual/jpa_overview_pc.xml
index 9102345e0..effa3fc8a 100644
--- a/openjpa-project/src/doc/manual/jpa_overview_pc.xml
+++ b/openjpa-project/src/doc/manual/jpa_overview_pc.xml
@@ -1069,7 +1069,7 @@ lifecycle events and their corresponding method markers are:
lifecycle callbacks
-
+
PrePersist: Methods marked with this annotation
will be invoked before an object is persisted. This could be used for assigning
primary key values to persistent objects. This is equivalent to the XML element
@@ -1086,7 +1086,7 @@ tag pre-persist.
lifecycle callbacks
-
+
PostPersist: Methods marked with this annotation
will be invoked after an object has transitioned to the persistent state. You
might want to use such methods to update a screen after a new row is added. This
@@ -1103,7 +1103,7 @@ is equivalent to the XML element tag post-persist.
lifecycle callbacks
-
+
PostLoad: Methods marked with this annotation
will be invoked after all eagerly fetched fields of your class have been loaded
from the datastore. No other persistent fields can be accessed in this method.
@@ -1125,7 +1125,7 @@ data structure.
lifecycle callbacks
-
+
PreUpdate: Methods marked with this annotation
will be invoked just the persistent values in your objects are flushed to the
datastore. This is equivalent to the XML element tag
@@ -1149,7 +1149,7 @@ persistent fields with information cached in non-persistent data.
lifecycle callbacks
-
+
PostUpdate: Methods marked with this annotation
will be invoked after changes to a given instance have been stored to the
datastore. This is useful for clearing stale data cached at the application
@@ -1166,7 +1166,7 @@ layer. This is equivalent to the XML element tag post-update.
lifecycle callbacks
-
+
PreRemove: Methods marked with this annotation
will be invoked before an object transactions to the deleted state. Access to
persistent fields is valid within this method. You might use this method to
@@ -1185,7 +1185,7 @@ pre-remove.
lifecycle callbacks
-
+
PostRemove: Methods marked with this annotation
will be invoked after an object has been marked as to be deleted. This is
equivalent to the XML element tag post-remove.
diff --git a/openjpa-project/src/doc/manual/jpa_overview_persistence.xml b/openjpa-project/src/doc/manual/jpa_overview_persistence.xml
index bfa9abfe3..105d2cbed 100644
--- a/openjpa-project/src/doc/manual/jpa_overview_persistence.xml
+++ b/openjpa-project/src/doc/manual/jpa_overview_persistence.xml
@@ -68,7 +68,7 @@ additional utility methods.
Within a container, you will typically use injection to
access an EntityManagerFactory. Applications operating
outside of a container, however, can use the
-
+
Persistence class to obtain
EntityManagerFactory objects in a vendor-neutral fashion.
@@ -456,7 +456,7 @@ transaction management.
provider: If you are using a third-party JPA vendor, this
element names its implementation of the
-
+
PersistenceProvider bootstrapping interface.
diff --git a/openjpa-project/src/doc/manual/jpa_overview_query.xml b/openjpa-project/src/doc/manual/jpa_overview_query.xml
index 3457845ab..5c438f852 100644
--- a/openjpa-project/src/doc/manual/jpa_overview_query.xml
+++ b/openjpa-project/src/doc/manual/jpa_overview_query.xml
@@ -74,7 +74,7 @@ public Query createQuery(String jpql);
The
-
+
EntityManager.createQuery method creates a
Query instance from a given JPQL string.
@@ -83,7 +83,7 @@ public List getResultList();
Invoking
-
+
Query.getResultList executes the query and
returns a List containing the matching objects. The
following example executes our Magazine query above:
diff --git a/openjpa-project/src/doc/manual/jpa_resources.xml b/openjpa-project/src/doc/manual/jpa_resources.xml
index 47f51109c..2eb8a6dec 100644
--- a/openjpa-project/src/doc/manual/jpa_resources.xml
+++ b/openjpa-project/src/doc/manual/jpa_resources.xml
@@ -35,7 +35,7 @@ Java Persistence 2.0 page
-
+
javax.persistence Javadoc
diff --git a/openjpa-project/src/doc/manual/ref_guide_caching.xml b/openjpa-project/src/doc/manual/ref_guide_caching.xml
index c1d596e6c..0ecbc1b49 100644
--- a/openjpa-project/src/doc/manual/ref_guide_caching.xml
+++ b/openjpa-project/src/doc/manual/ref_guide_caching.xml
@@ -820,7 +820,7 @@ public void evictAll();
For JPA queries with parameters, set the desired parameter values into the
-
+
Query instance before calling the above methods.
@@ -864,7 +864,7 @@ public void unpin(Query q);
For JPA queries with parameters, set the desired parameter values into the
-
+
Query instance before calling the above methods.
diff --git a/openjpa-project/src/doc/manual/ref_guide_deploy.xml b/openjpa-project/src/doc/manual/ref_guide_deploy.xml
index 11ac262bf..2774b2566 100644
--- a/openjpa-project/src/doc/manual/ref_guide_deploy.xml
+++ b/openjpa-project/src/doc/manual/ref_guide_deploy.xml
@@ -139,7 +139,7 @@ global transactions.
You can override the global transaction mode setting when you obtain an
EntityManager using the
-
+
EntityManagerFactory's
createEntityManager(Map props) method. Simply set the
openjpa.TransactionMode key of the given Map
diff --git a/openjpa-project/src/doc/manual/ref_guide_runtime.xml b/openjpa-project/src/doc/manual/ref_guide_runtime.xml
index 73ea9389f..17235d823 100644
--- a/openjpa-project/src/doc/manual/ref_guide_runtime.xml
+++ b/openjpa-project/src/doc/manual/ref_guide_runtime.xml
@@ -658,7 +658,7 @@ Returns the level at which the given object is currently locked.
In addition to the standard
-
+
EntityManager.lock(Object, LockModeType)
method, the
diff --git a/openjpa-project/src/doc/manual/ref_guide_slice.xml b/openjpa-project/src/doc/manual/ref_guide_slice.xml
index 8ebd81070..bb00b5cd6 100644
--- a/openjpa-project/src/doc/manual/ref_guide_slice.xml
+++ b/openjpa-project/src/doc/manual/ref_guide_slice.xml
@@ -601,7 +601,7 @@ the JDBC connection URL of a slice.
This plug-in property determines the policy for transaction commit
across multiple slices. The value of this property is a fully-qualified
class name that implements
-
+
javax.transaction.TransactionManager
interface.