You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openjpa.apache.org by mp...@apache.org on 2006/09/05 21:28:38 UTC
svn commit: r440450 [2/3] -
/incubator/openjpa/trunk/openjpa-project/src/doc/manual/
Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_conf.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_conf.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_conf.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_conf.xml Tue Sep 5 12:28:36 2006
@@ -95,7 +95,7 @@
<para>
All OpenJPA command-line tools accept flags that allow you to specify the
configuration resource to use, and to override any property.
-<xref linkend="ref_guide_conf_devtools"></xref> describes these flags.
+<xref linkend="ref_guide_conf_devtools"/> describes these flags.
</para>
</listitem>
</itemizedlist>
@@ -389,12 +389,12 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A comma-separated list of plugin
-strings (see <xref linkend="ref_guide_conf_plugins"></xref>) describing custom
+strings (see <xref linkend="ref_guide_conf_plugins"/>) describing custom
<ulink url="../apidocs/org/apache/openjpa/jdbc/kernel/exps/JDBCAggregateListener.html">
<classname> org.apache.openjpa.jdbc.kernel.exps.JDBCAggregateListener
</classname></ulink>s to make available to all queries, in addition to the
-standard set of listeners. See <xref linkend="ref_guide_enterprise_queryext">
-</xref> for details on aggregate listeners.
+standard set of listeners. See <xref linkend="ref_guide_enterprise_queryext"/>
+ for details on aggregate listeners.
</para>
</section>
<section id="openjpa.AutoClear">
@@ -522,7 +522,7 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/kernel/BrokerFactory.html">
<classname>org.apache.openjpa.kernel.BrokerFactory</classname></ulink> type to
use.
@@ -564,10 +564,10 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/kernel/Broker.html"><classname>
org.apache.openjpa.kernel.Broker</classname></ulink> type to use at runtime. See
-<xref linkend="ref_guide_runtime_pmextension"></xref> on for details.
+<xref linkend="ref_guide_runtime_pmextension"/> on for details.
</para>
</section>
<section id="openjpa.ClassResolver">
@@ -606,7 +606,7 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/util/ClassResolver.html"><classname>
org.apache.openjpa.util.ClassResolver</classname></ulink> implementation to use
for class name resolution. You may wish to plug in your own resolver if you have
@@ -688,7 +688,7 @@
<emphasis role="bold">Description:</emphasis> The full class name of either the
JDBC <classname>java.sql.Driver</classname>, or a <classname>
javax.sql.DataSource</classname> implementation to use to connect to the
-database. See <xref linkend="ref_guide_dbsetup"></xref> for details.
+database. See <xref linkend="ref_guide_dbsetup"/> for details.
</para>
</section>
<section id="openjpa.Connection2DriverName">
@@ -729,9 +729,9 @@
<para>
<emphasis role="bold">Description:</emphasis> This property is equivalent to the
<literal>openjpa.ConnectionDriverName</literal> property described in
-<xref linkend="openjpa.ConnectionDriverName"></xref>, but applies to the
+<xref linkend="openjpa.ConnectionDriverName"/>, but applies to the
alternate connection factory used for unmanaged connections. See
-<xref linkend="ref_guide_dbsetup_thirdparty_enlist"></xref> for details.
+<xref linkend="ref_guide_dbsetup_thirdparty_enlist"/> for details.
</para>
</section>
<section id="openjpa.ConnectionFactory">
@@ -771,7 +771,7 @@
<para>
<emphasis role="bold">Description:</emphasis> A <classname>javax.sql.DataSource
</classname> to use to connect to the database. See
-<xref linkend="ref_guide_dbsetup"></xref> for details.
+<xref linkend="ref_guide_dbsetup"/> for details.
</para>
</section>
<section id="openjpa.ConnectionFactory2">
@@ -811,7 +811,7 @@
<para>
<emphasis role="bold">Description:</emphasis> An unmanaged <classname>
javax.sql.DataSource</classname> to use to connect to the database. See
-<xref linkend="ref_guide_dbsetup"></xref> for details.
+<xref linkend="ref_guide_dbsetup"/> for details.
</para>
</section>
<section id="openjpa.ConnectionFactoryName">
@@ -852,7 +852,7 @@
<para>
<emphasis role="bold">Description:</emphasis> The JNDI location of a <classname>
javax.sql.DataSource</classname> to use to connect to the database. See
-<xref linkend="ref_guide_dbsetup"></xref> for details.
+<xref linkend="ref_guide_dbsetup"/> for details.
</para>
</section>
<section id="openjpa.ConnectionFactory2Name">
@@ -893,7 +893,7 @@
<para>
<emphasis role="bold">Description:</emphasis> The JNDI location of an unmanaged
<classname>javax.sql.DataSource</classname> to use to connect to the database.
-See <xref linkend="ref_guide_enterprise_xa"></xref> for details.
+See <xref linkend="ref_guide_enterprise_xa"/> for details.
</para>
</section>
<section id="openjpa.ConnectionFactoryMode">
@@ -938,7 +938,7 @@
<para>
<emphasis role="bold">Description:</emphasis> The connection factory mode to use
when integrating with the application server's managed transactions. See
-<xref linkend="ref_guide_dbsetup_thirdparty_enlist"></xref> for details.
+<xref linkend="ref_guide_dbsetup_thirdparty_enlist"/> for details.
</para>
</section>
<section id="openjpa.ConnectionFactoryProperties">
@@ -978,9 +978,9 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) listing properties for
+<xref linkend="ref_guide_conf_plugins"/>) listing properties for
configuration of the <classname>javax.sql.DataSource</classname> in use. See the
-<xref linkend="ref_guide_dbsetup"></xref> for details.
+<xref linkend="ref_guide_dbsetup"/> for details.
</para>
</section>
<section id="openjpa.ConnectionFactory2Properties">
@@ -1021,9 +1021,9 @@
<para>
<emphasis role="bold">Description:</emphasis> This property is equivalent to the
<literal>openjpa.ConnectionFactoryProperties</literal> property described in
-<xref linkend="openjpa.ConnectionFactoryProperties"></xref>, but applies to the
+<xref linkend="openjpa.ConnectionFactoryProperties"/>, but applies to the
alternate connection factory used for unmanaged connections. See
-<xref linkend="ref_guide_dbsetup_thirdparty_enlist"></xref> for details.
+<xref linkend="ref_guide_dbsetup_thirdparty_enlist"/> for details.
</para>
</section>
<section id="openjpa.ConnectionPassword">
@@ -1063,7 +1063,7 @@
<para>
<emphasis role="bold">Description:</emphasis> The password for the user
specified in the <literal>ConnectionUserName</literal> property. See
-<xref linkend="ref_guide_dbsetup"></xref> for details.
+<xref linkend="ref_guide_dbsetup"/> for details.
</para>
</section>
<section id="openjpa.Connection2Password">
@@ -1103,9 +1103,9 @@
<para>
<emphasis role="bold">Description:</emphasis> This property is equivalent to the
<literal>openjpa.ConnectionPassword</literal> property described in
-<xref linkend="openjpa.ConnectionPassword"></xref>, but applies to the
+<xref linkend="openjpa.ConnectionPassword"/>, but applies to the
alternate connection factory used for unmanaged connections. See
-<xref linkend="ref_guide_dbsetup_thirdparty_enlist"></xref> for details.
+<xref linkend="ref_guide_dbsetup_thirdparty_enlist"/> for details.
</para>
</section>
<section id="openjpa.ConnectionProperties">
@@ -1145,9 +1145,9 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) listing properties to configure
+<xref linkend="ref_guide_conf_plugins"/>) listing properties to configure
the driver listed in the <literal>ConnectionDriverName</literal> property
-described below. See <xref linkend="ref_guide_dbsetup"></xref> for details.
+described below. See <xref linkend="ref_guide_dbsetup"/> for details.
</para>
</section>
<section id="openjpa.Connection2Properties">
@@ -1188,9 +1188,9 @@
<para>
<emphasis role="bold">Description:</emphasis> This property is equivalent to the
<literal>openjpa.ConnectionProperties</literal> property described in
-<xref linkend="openjpa.ConnectionProperties"></xref>, but applies to the
+<xref linkend="openjpa.ConnectionProperties"/>, but applies to the
alternate connection factory used for unmanaged connections. See
-<xref linkend="ref_guide_dbsetup_thirdparty_enlist"></xref> for details.
+<xref linkend="ref_guide_dbsetup_thirdparty_enlist"/> for details.
</para>
</section>
<section id="openjpa.ConnectionURL">
@@ -1229,7 +1229,7 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> The JDBC URL for the database. See
-<xref linkend="ref_guide_dbsetup"></xref> for details.
+<xref linkend="ref_guide_dbsetup"/> for details.
</para>
</section>
<section id="openjpa.Connection2URL">
@@ -1269,9 +1269,9 @@
<para>
<emphasis role="bold">Description:</emphasis> This property is equivalent to the
<literal>openjpa.ConnectionURL</literal> property described in
-<xref linkend="openjpa.ConnectionURL"></xref>, but applies to the alternate
+<xref linkend="openjpa.ConnectionURL"/>, but applies to the alternate
connection factory used for unmanaged connections. See
-<xref linkend="ref_guide_dbsetup_thirdparty_enlist"></xref> for details.
+<xref linkend="ref_guide_dbsetup_thirdparty_enlist"/> for details.
</para>
</section>
<section id="openjpa.ConnectionUserName">
@@ -1310,7 +1310,7 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> The user name to use when
-connecting to the database. See the <xref linkend="ref_guide_dbsetup"></xref>
+connecting to the database. See the <xref linkend="ref_guide_dbsetup"/>
for details.
</para>
</section>
@@ -1351,9 +1351,9 @@
<para>
<emphasis role="bold">Description:</emphasis> This property is equivalent to the
<literal>openjpa.ConnectionUserName</literal> property described in
-<xref linkend="openjpa.ConnectionUserName"></xref>, but applies to the
+<xref linkend="openjpa.ConnectionUserName"/>, but applies to the
alternate connection factory used for unmanaged connections. See
-<xref linkend="ref_guide_dbsetup_thirdparty_enlist"></xref> for details.
+<xref linkend="ref_guide_dbsetup_thirdparty_enlist"/> for details.
</para>
</section>
<section id="openjpa.ConnectionRetainMode">
@@ -1394,7 +1394,7 @@
<para>
<emphasis role="bold">Description:</emphasis> Controls how OpenJPA uses
datastore connections. This property can also be specified for individual
-sessions. See <xref linkend="ref_guide_dbsetup_retain"></xref> for details.
+sessions. See <xref linkend="ref_guide_dbsetup_retain"/> for details.
</para>
</section>
<section id="openjpa.DataCache">
@@ -1433,10 +1433,10 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin list string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/datacache/DataCache.html"><classname>
org.apache.openjpa.datacache.DataCache</classname></ulink>s to use for data
-caching. See <xref linkend="ref_guide_cache_conf"></xref> for details.
+caching. See <xref linkend="ref_guide_cache_conf"/> for details.
</para>
</section>
<section id="openjpa.DataCacheManager">
@@ -1475,10 +1475,10 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/datacache/DataCacheManager.html">
<classname>openjpa.datacache.DataCacheManager</classname></ulink> that manages
-the system data caches. See <xref linkend="ref_guide_cache"></xref> for details
+the system data caches. See <xref linkend="ref_guide_cache"/> for details
on data caching.
</para>
</section>
@@ -1520,7 +1520,7 @@
<emphasis role="bold">Description:</emphasis> The number of milliseconds that
data in the data cache is valid. Set this to -1 to indicate that data should not
expire from the cache. This property can also be specified for individual
-classes. See <xref linkend="ref_guide_cache_conf"></xref> for details.
+classes. See <xref linkend="ref_guide_cache_conf"/> for details.
</para>
</section>
<section id="openjpa.DetachState">
@@ -1567,7 +1567,7 @@
<para>
<emphasis role="bold">Description:</emphasis> Determines which fields are part
of the detached graph and related options. For more details, see
-<xref linkend="ref_guide_detach_graph"></xref>.
+<xref linkend="ref_guide_detach_graph"/>.
</para>
</section>
<section id="openjpa.DynamicDataStructs">
@@ -1662,7 +1662,7 @@
<para>
<emphasis role="bold">Description:</emphasis> The number of rows to fetch at
once when scrolling through a result set. The fetch size can also be set at
-runtime. See <xref linkend="ref_guide_dbsetup_lrs"></xref> for details.
+runtime. See <xref linkend="ref_guide_dbsetup_lrs"/> for details.
</para>
</section>
<section id="openjpa.FetchGroups">
@@ -1697,8 +1697,8 @@
<para>
<emphasis role="bold">Description:</emphasis> A comma-separated list of fetch
group names that are to be loaded when retrieving objects from the datastore.
-Fetch groups can also be set at runtime. See <xref linkend="ref_guide_fetch">
-</xref> for details.
+Fetch groups can also be set at runtime. See <xref linkend="ref_guide_fetch"/>
+ for details.
</para>
</section>
<section id="openjpa.FilterListeners">
@@ -1737,12 +1737,12 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A comma-separated list of full
-plugin strings (see <xref linkend="ref_guide_conf_plugins"></xref>) for custom
+plugin strings (see <xref linkend="ref_guide_conf_plugins"/>) for custom
<ulink url="../apidocs/org/apache/openjpa/jdbc/kernel/exps/JDBCFilterListener.html">
<classname> org.apache.openjpa.jdbc.kernel.exps.JDBCFilterListener</classname>
</ulink>s to make available to all queries, in addition to the standard set of
listeners. You can also add filter listeners to individual queries. See
-<xref linkend="ref_guide_enterprise_queryext"></xref> for details.
+<xref linkend="ref_guide_enterprise_queryext"/> for details.
</para>
</section>
<section id="openjpa.FlushBeforeQueries">
@@ -1794,7 +1794,7 @@
<para>
<emphasis role="bold">Description:</emphasis> Whether or not to flush any
changes made in the current transaction to the datastore before executing a
-query. See <xref linkend="ref_guide_dbsetup_retain"></xref> for details.
+query. See <xref linkend="ref_guide_dbsetup_retain"/> for details.
</para>
</section>
<section id="openjpa.IgnoreChanges">
@@ -1873,11 +1873,11 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing a
+<xref linkend="ref_guide_conf_plugins"/>) describing a
<ulink url="../apidocs/org/apache/openjpa/kernel/InverseManager.html">
<classname>org.apache.openjpa.kernel.InverseManager</classname></ulink> to use
for managing bidirectional relations upon a flush. See
-<xref linkend="ref_guide_inverses"></xref> for usage documentation.
+<xref linkend="ref_guide_inverses"/> for usage documentation.
</para>
</section>
<section id="openjpa.LockManager">
@@ -1920,7 +1920,7 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing a
+<xref linkend="ref_guide_conf_plugins"/>) describing a
<ulink url="../apidocs/org/apache/openjpa/kernel/LockManager.html"><classname>
org.apache.openjpa.kernel.LockManager</classname></ulink> to use for acquiring
locks on persistent instances during transactions.
@@ -1963,7 +1963,7 @@
<para>
<emphasis role="bold">Description:</emphasis> The number of milliseconds to wait
for an object lock before throwing an exception, or -1 for no limit. See
-<xref linkend="ref_guide_locking"></xref> for details.
+<xref linkend="ref_guide_locking"/> for details.
</para>
</section>
<section id="openjpa.Log">
@@ -2005,10 +2005,10 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing a
+<xref linkend="ref_guide_conf_plugins"/>) describing a
<ulink url="../apidocs/org/apache/openjpa/lib/log/LogFactory.html"><classname>
org.apache.openjpa.lib.log.LogFactory</classname></ulink> to use for logging.
-For details on logging, see <xref linkend="ref_guide_logging"></xref>.
+For details on logging, see <xref linkend="ref_guide_logging"/>.
</para>
</section>
<section id="openjpa.ManagedRuntime">
@@ -2050,7 +2050,7 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/ee/ManagedRuntime.html"><classname>
org.apache.openjpa.ee.ManagedRuntime</classname></ulink> implementation to use
for obtaining a reference to the <classname>TransactionManager</classname> in an
@@ -2167,11 +2167,11 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/meta/MetaDataFactory.html">
<classname>openjpa.meta.MetaDataFactory</classname></ulink> to use to store and
retrieve metadata for your persistent classes. See
-<xref linkend="ref_guide_meta_factory"></xref> for details.
+<xref linkend="ref_guide_meta_factory"/> for details.
</para>
</section>
<section id="openjpa.Multithreaded">
@@ -2292,11 +2292,11 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing a
+<xref linkend="ref_guide_conf_plugins"/>) describing a
<ulink url="../apidocs/org/apache/openjpa/event/OrphanedKeyAction.html">
<classname>org.apache.openjpa.event.OrphanedKeyAction</classname></ulink> to
invoke when OpenJPA discovers an orphaned datastore key. See
-<xref linkend="ref_guide_orphan"></xref> for details.
+<xref linkend="ref_guide_orphan"/> for details.
</para>
</section>
<section id="openjpa.NontransactionalRead">
@@ -2400,11 +2400,11 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing a
+<xref linkend="ref_guide_conf_plugins"/>) describing a
<ulink url="../apidocs/org/apache/openjpa/util/ProxyManager.html"><classname>
org.apache.openjpa.util.ProxyManager</classname></ulink> to use for proxying
mutable second class objects. See
-<xref linkend="ref_guide_pc_scos_proxy_custom"></xref> for details.
+<xref linkend="ref_guide_pc_scos_proxy_custom"/> for details.
</para>
</section>
<section id="openjpa.QueryCache">
@@ -2440,16 +2440,16 @@
</para>
<para>
<emphasis role="bold">Default:</emphasis><literal>true</literal>, when the data
-cache (see <xref linkend="openjpa.DataCache"></xref>) is also enabled, <literal>
+cache (see <xref linkend="openjpa.DataCache"/>) is also enabled, <literal>
false</literal> otherwise.
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/datacache/QueryCache.html">
<classname>org.apache.openjpa.datacache.QueryCache</classname></ulink>
implementation to use for caching of queries loaded from the data store. See
-<xref linkend="ref_guide_cache_query"></xref> for details.
+<xref linkend="ref_guide_cache_query"/> for details.
</para>
</section>
<section id="openjpa.QueryCompilationCache">
@@ -2489,9 +2489,9 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the <literal>
+<xref linkend="ref_guide_conf_plugins"/>) describing the <literal>
java.util.Map</literal> to use for caching of data used during query
-compilation. See <xref linkend="ref_guide_cache_querycomp"></xref> for details.
+compilation. See <xref linkend="ref_guide_cache_querycomp"/> for details.
</para>
</section>
<section id="openjpa.ReadLockLevel">
@@ -2585,11 +2585,11 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/event/RemoteCommitProvider.html">
<classname>org.apache.openjpa.event.RemoteCommitProvider</classname></ulink>
implementation to use for distributed event notification. See
-<xref linkend="ref_guide_event_conf"></xref> for more information.
+<xref linkend="ref_guide_event_conf"/> for more information.
</para>
</section>
<section id="openjpa.RestoreState">
@@ -2728,11 +2728,11 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing a
+<xref linkend="ref_guide_conf_plugins"/>) describing a
<ulink url="javadoc/openjpa/kernel/SavepointManager.html"><classname>
org.apache.openjpa.kernel.SavepointManager</classname></ulink> to use for
-managing transaction savepoints. See <xref linkend="ref_guide_savepoints">
-</xref> for details.
+managing transaction savepoints. See <xref linkend="ref_guide_savepoints"/>
+ for details.
</para>
</section>
<section id="openjpa.Sequence">
@@ -2763,10 +2763,10 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/kernel/Seq.html"><classname>
org.apache.openjpa.kernel.Seq</classname></ulink> implementation to use for the
-system sequence. See <xref linkend="ref_guide_sequence"></xref> for more
+system sequence. See <xref linkend="ref_guide_sequence"/> for more
information.
</para>
</section>
@@ -2912,7 +2912,7 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A comma-separated list of plugin
-strings (see <xref linkend="ref_guide_conf_plugins"></xref>) describing
+strings (see <xref linkend="ref_guide_conf_plugins"/>) describing
<ulink url="../apidocs/org/apache/openjpa/lib/jdbc/ConnectionDecorator.html">
<classname>org.apache.openjpa.lib.jdbc.ConnectionDecorator</classname></ulink>
instances to install on the connection factory. These decorators can wrap
@@ -2962,14 +2962,14 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/jdbc/sql/DBDictionary.html">
<classname>org.apache.openjpa.jdbc.sql.DBDictionary</classname></ulink> to use
for database interaction. OpenJPA typically auto-configures the dictionary based
on the JDBC URL, but you may have to set this property explicitly if you are
using an unrecognized driver, or to plug in your own dictionary for a database
OpenJPA <phrase>JPA</phrase> does not support out-of-the-box. See
-<xref linkend="ref_guide_dbsetup_dbsupport"></xref> for details.
+<xref linkend="ref_guide_dbsetup_dbsupport"/> for details.
</para>
</section>
<section id="openjpa.jdbc.DriverDataSource">
@@ -3016,7 +3016,7 @@
<ulink url="../apidocs/org/apache/openjpa/jdbc/schema/OpenJPAPoolingDataSource">
<classname>org.apache.openjpa.jdbc.schema.OpenJPAPoolingDataSource</classname>
</ulink>, will perform connection pooling as described at
-<xref linkend="ref_guide_dbsetup"></xref>.
+<xref linkend="ref_guide_dbsetup"/>.
</para>
</section>
<section id="openjpa.jdbc.EagerFetchMode">
@@ -3060,7 +3060,7 @@
<para>
<emphasis role="bold">Description:</emphasis> Optimizes how OpenJPA loads
persistent relations. This setting can also be varied at runtime. See
-<xref linkend="ref_guide_perfpack_eager"></xref> for details.
+<xref linkend="ref_guide_perfpack_eager"/> for details.
</para>
</section>
<section id="openjpa.jdbc.FetchDirection">
@@ -3104,7 +3104,7 @@
<para>
<emphasis role="bold">Description:</emphasis> The expected order in which query
result lists will be accessed. This property can also be varied at runtime. See
-<xref linkend="ref_guide_dbsetup_lrs"></xref> for details.
+<xref linkend="ref_guide_dbsetup_lrs"/> for details.
</para>
</section>
<section id="openjpa.jdbc.JDBCListeners">
@@ -3143,7 +3143,7 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A comma-separated list of plugin
-strings (see <xref linkend="ref_guide_conf_plugins"></xref>) describing
+strings (see <xref linkend="ref_guide_conf_plugins"/>) describing
<ulink url="../apidocs/org/apache/openjpa/lib/jdbc/JDBCListener.html">
<classname>org.apache.openjpa.lib.jdbc.JDBCListener</classname></ulink> event
listeners to install. These listeners will be notified on various JDBC-related
@@ -3191,7 +3191,7 @@
<para>
<emphasis role="bold">Description:</emphasis> The strategy to use to calculate
the size of a result list. This property can also be varied at runtime. See
-<xref linkend="ref_guide_dbsetup_lrs"></xref> for details.
+<xref linkend="ref_guide_dbsetup_lrs"/> for details.
</para>
</section>
<section id="openjpa.jdbc.MappingDefaults">
@@ -3234,11 +3234,11 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/jdbc/meta/MappingDefaults.html">
<classname>org.apache.openjpa.jdbc.meta.MappingDefaults</classname></ulink> to
use to define default column names, table names, and constraints for your
-persistent classes. See <xref linkend="ref_guide_mapping_factory"></xref> for
+persistent classes. See <xref linkend="ref_guide_mapping_factory"/> for
details.
</para>
</section>
@@ -3282,11 +3282,11 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/meta/MetaDataFactory.html">
<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"></xref> for details.
+classes. See <xref linkend="ref_guide_mapping_factory"/> for details.
</para>
</section>
<section id="openjpa.jdbc.ResultSetType">
@@ -3330,7 +3330,7 @@
<para>
<emphasis role="bold">Description:</emphasis> The JDBC result set type to use
when fetching result lists. This property can also be varied at runtime. See
-<xref linkend="ref_guide_dbsetup_lrs"></xref> for details.
+<xref linkend="ref_guide_dbsetup_lrs"/> for details.
</para>
</section>
<section id="openjpa.jdbc.Schema">
@@ -3365,7 +3365,7 @@
<para>
<emphasis role="bold">Description:</emphasis> The default schema name to prepend
to unqualified table names. Also, the schema in which OpenJPA will create new
-tables. See <xref linkend="ref_guide_schema_def"></xref> for details.
+tables. See <xref linkend="ref_guide_schema_def"/> for details.
</para>
</section>
<section id="openjpa.jdbc.SchemaFactory">
@@ -3409,11 +3409,11 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/jdbc/schema/SchemaFactory.html">
<classname>org.apache.openjpa.jdbc.schema.SchemaFactory</classname></ulink> to
use to store and retrieve information about the database schema. See
-<xref linkend="ref_guide_schema_info_factory"></xref> for details.
+<xref linkend="ref_guide_schema_info_factory"/> for details.
</para>
</section>
<section id="openjpa.jdbc.Schemas">
@@ -3448,7 +3448,7 @@
<para>
<emphasis role="bold">Description:</emphasis> A comma-separated list of the
schemas and/or tables used for your persistent data. See
-<xref linkend="ref_guide_schema_info_list"></xref> for details.
+<xref linkend="ref_guide_schema_info_list"/> for details.
</para>
</section>
<section id="openjpa.jdbc.SQLFactory">
@@ -3487,10 +3487,10 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> A plugin string (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing the
+<xref linkend="ref_guide_conf_plugins"/>) describing the
<ulink url="../apidocs/org/apache/openjpa/jdbc/sql/SQLFactory.html"><classname>
org.apache.openjpa.jdbc.sql.SQLFactory</classname></ulink> to use to abstract
-common SQL constructs. See <xref linkend="ref_guide_dbsetup_sqlfactory"></xref>
+common SQL constructs. See <xref linkend="ref_guide_dbsetup_sqlfactory"/>
for details.
</para>
</section>
@@ -3543,7 +3543,7 @@
<para>
<emphasis role="bold">Description:</emphasis> How to select subclass data when
it is in other tables. This setting can also be varied at runtime. See
-<xref linkend="ref_guide_perfpack_eager"></xref>.
+<xref linkend="ref_guide_perfpack_eager"/>.
</para>
</section>
<section id="openjpa.jdbc.SynchronizeMappings">
@@ -3585,7 +3585,7 @@
<emphasis role="bold">Description:</emphasis> Controls whether OpenJPA will
attempt to run the mapping tool on all persistent classes to synchronize their
mappings and schema at runtime. Useful for rapid test/debug cycles. See
-<xref linkend="ref_guide_mapping_synch"></xref> for more information.
+<xref linkend="ref_guide_mapping_synch"/> for more information.
</para>
</section>
<section id="openjpa.jdbc.TransactionIsolation">
@@ -3639,7 +3639,7 @@
</para>
<para>
<emphasis role="bold">Description:</emphasis> The JDBC transaction isolation
-level to use. See <xref linkend="ref_guide_dbsetup_isolation"></xref> for
+level to use. See <xref linkend="ref_guide_dbsetup_isolation"/> for
details.
</para>
</section>
Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml Tue Sep 5 12:28:36 2006
@@ -87,7 +87,7 @@
To configure advanced features such as connection pooling and prepared statement
caching, or to configure the underlying JDBC driver, use the following optional
properties. The syntax of these property strings follows the syntax of OpenJPA
-plugin parameters described in <xref linkend="ref_guide_conf_plugins"></xref>.
+plugin parameters described in <xref linkend="ref_guide_conf_plugins"/>.
</para>
<itemizedlist>
<listitem>
@@ -377,10 +377,10 @@
Validation SQL Defaults
</title>
<tgroup cols="2" align="left" colsep="1" rowsep="1">
- <colspec colname="db">
- </colspec>
- <colspec colname="sql">
- </colspec>
+ <colspec colname="db"/>
+
+ <colspec colname="sql"/>
+
<thead>
<row>
<entry colname="db">
@@ -480,7 +480,7 @@
</table>
<para>
To disable validation SQL, set this property to an empty string, as in
-<xref linkend="ref_guide_dbsetup_builtin_ex"></xref>
+<xref linkend="ref_guide_dbsetup_builtin_ex"/>
</para>
</listitem>
<listitem>
@@ -802,12 +802,12 @@
second <classname> DataSource</classname> just as the first, but use the various
"2" connection properties, such as <literal>openjpa.ConnectionFactory2Name
</literal> or <literal>openjpa.Connection2DriverName</literal>. These
-properties are outlined in <xref linkend="ref_guide_conf"></xref>. <phrase> If
+properties are outlined in <xref linkend="ref_guide_conf"/>. <phrase> If
your second <classname>DataSource</classname> is also bound to JNDI, you can use
JPA XML's <literal>non-jta-data-source</literal> to specify its location.
</phrase> Typically, <phrase>though,</phrase> you will use OpenJPA's built-in
implementation for the second <classname>DataSource</classname> (see
-<xref linkend="ref_guide_dbsetup_builtin"></xref> ).
+<xref linkend="ref_guide_dbsetup_builtin"/> ).
</para>
<example id="ref_guide_enterprise_xa_conf_ex">
<title>
@@ -941,7 +941,7 @@
<para>
OpenJPA <phrase>JPA</phrase> can take advantage of any JDBC 2.x compliant
driver, making almost any major database a candidate for use. See our officially
-supported database list in <xref linkend="supported_databases"></xref> for more
+supported database list in <xref linkend="supported_databases"/> for more
information. Typically, OpenJPA auto-configures its JDBC behavior and SQL
dialect for your database, based on the values of your connection-related
configuration properties.
@@ -1582,7 +1582,7 @@
</secondary>
</indexterm>
<literal>JoinSyntax</literal>: The SQL join syntax to use in select statements.
-See <xref linkend="ref_guide_dbsetup_sql92"></xref>.
+See <xref linkend="ref_guide_dbsetup_sql92"/>.
</para>
</listitem>
<listitem id="DBDictionary.CrossJoinClause">
@@ -2959,8 +2959,8 @@
assume that the current sequence value from the sequence specified in the
<literal>AutoAssignSequenceName</literal> parameter will hold the value of the
new primary key for rows that have been inserted. For more details on
-auto-increment support, see <xref linkend="ref_guide_pc_oid_pkgen_autoinc">
-</xref>.
+auto-increment support, see <xref linkend="ref_guide_pc_oid_pkgen_autoinc"/>
+.
</para>
</listitem>
<listitem id="OracleDictionary.AutoAssignSequenceName">
@@ -3093,7 +3093,7 @@
</indexterm>
<literal>BatchLimit</literal>: The maximum number of SQL update statements to
batch together. Set to 0 to disable statement batching, or -1 for no limit. See
-<xref linkend="ref_guide_perfpack_batch"></xref>.
+<xref linkend="ref_guide_perfpack_batch"/>.
</para>
</listitem>
<listitem id="SQLFactory.BatchParameterLimit">
@@ -3335,8 +3335,8 @@
</itemizedlist>
<para>
You can change the join syntax at runtime through the OpenJPA fetch
-configuration API, which is described in <xref linkend="ref_guide_runtime">
-</xref>.
+configuration API, which is described in <xref linkend="ref_guide_runtime"/>
+.
</para>
<example id="ref_guide_dbsetup_sql92_conf">
<title>
@@ -3446,7 +3446,7 @@
You can also specify the connection retain mode of individual <classname>
EntityManager</classname>s when you retrieve them from the <classname>
EntityManagerFactory</classname>. See
-<xref linkend="ref_guide_runtime_emfactory"></xref> for details.
+<xref linkend="ref_guide_runtime_emfactory"/> for details.
</para>
<para>
<indexterm>
@@ -3493,7 +3493,7 @@
</itemizedlist>
<para>
The flush mode can also be varied at runtime using the OpenJPA fetch
-configuration API, discussed in <xref linkend="ref_guide_runtime"></xref>.
+configuration API, discussed in <xref linkend="ref_guide_runtime"/>.
</para>
<para>
<indexterm>
@@ -3514,16 +3514,16 @@
OpenJPA Automatic Flush Behavior
</title>
<tgroup rowsep="1" colsep="1" align="left" cols="5">
- <colspec colname="col1">
- </colspec>
- <colspec colname="col2">
- </colspec>
- <colspec colname="col3">
- </colspec>
- <colspec colname="col4">
- </colspec>
- <colspec colname="col5">
- </colspec>
+ <colspec colname="col1"/>
+
+ <colspec colname="col2"/>
+
+ <colspec colname="col3"/>
+
+ <colspec colname="col4"/>
+
+ <colspec colname="col5"/>
+
<thead>
<row>
<entry colname="col1">
@@ -3755,7 +3755,7 @@
<para>
You can also configure on-demand loading for individual collection and map
fields via large result set proxies. See
-<xref linkend="ref_guide_pc_scos_proxy_lrs"></xref>.
+<xref linkend="ref_guide_pc_scos_proxy_lrs"/>.
</para>
</note>
<para>
@@ -3912,7 +3912,7 @@
<para>
Many <link linkend="ref_guide_runtime">OpenJPA runtime components</link> also
have methods to configure these properties on a case-by-case basis through their
-fetch configuration. See <xref linkend="ref_guide_runtime"></xref>.
+fetch configuration. See <xref linkend="ref_guide_runtime"/>.
</para>
<example id="ref_guide_dbsetup_lrs_runtime">
<title>
@@ -3959,7 +3959,7 @@
<para>
The <literal>Schema</literal> property also establishes the default schema for
new tables created through OpenJPA tools, such as the mapping tool covered in
-<xref linkend="ref_guide_mapping_mappingtool"></xref>.
+<xref linkend="ref_guide_mapping_mappingtool"/>.
</para>
</section>
<section id="ref_guide_schema_info">
@@ -4141,8 +4141,8 @@
</itemizedlist>
<para>
You can switch freely between schema factories at any time. The XML file format
-used by some factories is detailed in <xref linkend="ref_guide_schema_xml">
-</xref>. As with any OpenJPA plugin, you can can also implement your own schema
+used by some factories is detailed in <xref linkend="ref_guide_schema_xml"/>
+. As with any OpenJPA plugin, you can can also implement your own schema
factory if you have needs not met by the existing options.
</para>
</section>
@@ -4250,7 +4250,7 @@
on the schema, whether to reflect on tables and sequences whose names start with
<literal>OPENJPA_</literal>. Certain OpenJPA components may use such tables -
for example, the <literal>table</literal> schema factory option covered in
-<xref linkend="ref_guide_schema_info_factory"></xref>. When using other
+<xref linkend="ref_guide_schema_info_factory"/>. When using other
actions, <literal>openjpaTables</literal> controls whether these tables can be
dropped. Defaults to <literal>false</literal>.
</para>
Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_deploy.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_deploy.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_deploy.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_deploy.xml Tue Sep 5 12:28:36 2006
@@ -35,7 +35,7 @@
The JPA Overview describes the <classname>javax.persistence.Persistence
</classname> class. You can use <classname>Persistence</classname> to obtain
<classname>EntityManagerFactory</classname> instances, as demonstrated in
-<xref linkend="jpa_overview_persistence"></xref>. OpenJPA also extends
+<xref linkend="jpa_overview_persistence"/>. OpenJPA also extends
<classname>Persistence</classname> to add additional <classname>
EntityManagerFactory</classname> creation methods. The <classname>
org.apache.openjpa.persistence.OpenJPAPersistence</classname> class
@@ -147,7 +147,7 @@
<para>
Point OpenJPA at an enlisted <classname>XADataSource</classname>, and configure
a second non-enlisted data source. See
-<xref linkend="ref_guide_dbsetup_thirdparty_enlist"></xref>.
+<xref linkend="ref_guide_dbsetup_thirdparty_enlist"/>.
</para>
</listitem>
</orderedlist>
Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_integration.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_integration.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_integration.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_integration.xml Tue Sep 5 12:28:36 2006
@@ -172,7 +172,7 @@
Finally, tasks that invoke code-generation tools like the application identity
tool and reverse mapping tool accept a nested <literal>codeformat</literal>
element. See the code formatting documentation in
-<xref linkend="ref_guide_conf_devtools_format"></xref> for a list of code
+<xref linkend="ref_guide_conf_devtools_format"/> for a list of code
formatting attributes.
</para>
<example id="ref_guide_integration_conf_codeformat">
Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_logging.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_logging.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_logging.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_logging.xml Tue Sep 5 12:28:36 2006
@@ -59,9 +59,9 @@
and Ant tools. Most messages are basic statements detailing which classes or
files the tools are running on. Detailed output is only available via the
logging category the tool belongs to, such as <literal>openjpa.Enhance</literal>
-for the enhancer (see <xref linkend="ref_guide_pc_enhance"></xref>) or <literal>
+for the enhancer (see <xref linkend="ref_guide_pc_enhance"/>) or <literal>
openjpa.MetaData</literal> for the mapping tool (see
-<xref linkend="ref_guide_mapping_mappingtool"></xref> ). This logging category
+<xref linkend="ref_guide_mapping_mappingtool"/> ). This logging category
is provided so that you can get a general idea of what a tool is doing without
having to manipulate logging settings that might also affect runtime behavior.
</para>
@@ -548,7 +548,7 @@
To make OpenJPA use your custom log factory, set the
<link linkend="openjpa.Log"><literal>openjpa.Log</literal></link> configuration
property to your factory's full class name. Because this property is a plugin
-property (see <xref linkend="ref_guide_conf_plugins"></xref> ), you can also
+property (see <xref linkend="ref_guide_conf_plugins"/> ), you can also
pass parameters to your factory. For example, to use the example factory above
and set its prefix to "LOG MSG", you would set the <literal>openjpa.Log
</literal> property to the following string:
Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_mapping.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_mapping.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_mapping.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_mapping.xml Tue Sep 5 12:28:36 2006
@@ -8,7 +8,7 @@
</primary>
</indexterm>
<para>
-The JPA Overview's <xref linkend="jpa_overview_mapping"></xref> explains
+The JPA Overview's <xref linkend="jpa_overview_mapping"/> explains
object-relational mapping under JPA. This chapter reviews the mapping utilities
OpenJPA provides and examines OpenJPA features that go beyond the JPA
specification.
@@ -53,7 +53,7 @@
</para>
<note>
<para>
-<xref linkend="ref_guide_integration_mappingtool"></xref> describes the mapping
+<xref linkend="ref_guide_integration_mappingtool"/> describes the mapping
tool Ant task.
</para>
</note>
@@ -76,7 +76,7 @@
<literal>-schemaAction/-sa <add | refresh | drop | build | retain | none>
</literal>: The action to take on the schema. These options correspond to the
same-named actions on the schema tool described in
-<xref linkend="ref_guide_schema_schematool"></xref>. Unless you are running the
+<xref linkend="ref_guide_schema_schematool"/>. Unless you are running the
mapping tool on all of your persistent types at once or dropping a mapping, we
strongly recommend you use the default <literal>add</literal> action or the
<literal>build</literal> action. Otherwise you may end up inadvertently dropping
@@ -185,7 +185,7 @@
<listitem>
<para>
<literal>buildSchema</literal>: This is the default action when using JPA
-mapping defaults (see <xref linkend="ref_guide_mapping_defaults"></xref> ). It
+mapping defaults (see <xref linkend="ref_guide_mapping_defaults"/> ). It
makes the database schema match your existing mappings. If your provided
mappings conflict with a class definition, OpenJPA will fail with an informative
exception.
@@ -222,11 +222,11 @@
<para>
If you do not supply any arguments to the mapping tool, it will run on the
classes in your persistent classes list (see
-<xref linkend="ref_guide_pc_pcclasses"></xref> ).
+<xref linkend="ref_guide_pc_pcclasses"/> ).
</para>
<para>
The mappings generated by the mapping tool are stored by the system <emphasis>
-mapping factory</emphasis>. <xref linkend="ref_guide_mapping_factory"></xref>
+mapping factory</emphasis>. <xref linkend="ref_guide_mapping_factory"/>
discusses your mapping factory options.
</para>
<section id="ref_guide_mapping_mappingtool_examples">
@@ -244,11 +244,11 @@
<para>
The JPA specification defines a comprehensive set of defaults for missing
mapping information. Thus, forward mapping in JPA is virtually automatic. After
-using the mapping annotations covered in <xref linkend="jpa_overview_mapping">
-</xref> of the JPA Overview to override any unsatisfactory defaults, run the
+using the mapping annotations covered in <xref linkend="jpa_overview_mapping"/>
+ of the JPA Overview to override any unsatisfactory defaults, run the
mapping tool's <literal>buildSchema</literal> action on your persistent classes.
This is the default action when you use JPA mapping defaults (see
-<xref linkend="ref_guide_mapping_defaults"></xref> ).
+<xref linkend="ref_guide_mapping_defaults"/> ).
</para>
<para>
The <literal>buildSchema</literal> action manipulates the database schema to
@@ -356,8 +356,8 @@
</para>
<para>
In order to enable automatic runtime mapping, you must first list all your
-persistent classes as described in <xref linkend="ref_guide_pc_pcclasses">
-</xref>.
+persistent classes as described in <xref linkend="ref_guide_pc_pcclasses"/>
+.
</para>
<para>
OpenJPA will run the mapping tool on these classes when your application obtains
@@ -365,7 +365,7 @@
</para>
<para>
The <literal>openjpa.jdbc.SynchronizeMappings</literal> property is a plugin
-string (see <xref linkend="ref_guide_conf_plugins"></xref>) where the class
+string (see <xref linkend="ref_guide_conf_plugins"/>) where the class
name is the mapping tool action to invoke, and the properties are the
<classname>MappingTool</classname> class' JavaBean properties. These properties
correspond go the long versions of the tool's command line flags.
@@ -419,7 +419,7 @@
persistent class definitions, complete with metadata, from an existing database
schema. You do not have to use the reverse mapping tool to access an existing
schema; you are free to write your classes and mappings yourself, as described
-in <xref linkend="ref_guide_mapping_middle"></xref>. The reverse mapping tool,
+in <xref linkend="ref_guide_mapping_middle"/>. The reverse mapping tool,
however, can give you an excellent starting point from which to grow your
persistent classes.
</para>
@@ -455,7 +455,7 @@
Examine the generated schema file. JDBC drivers often provide incomplete or
faulty metadata, in which case the file will not exactly match the actual
schema. Alter the XML file to match the true schema. The XML format for the
-schema file is described in <xref linkend="ref_guide_schema_xml"></xref>.
+schema file is described in <xref linkend="ref_guide_schema_xml"/>.
</para>
<para>
After fixing any errors in the schema file, modify the XML to include foreign
@@ -496,7 +496,7 @@
comma-separated list of schema and table names to reverse map, if no XML schema
file is supplied. Each element of the list must follow the naming conventions
for the <literal>openjpa.jdbc.Schemas</literal> property described in
-<xref linkend="ref_guide_schema_info_list"></xref>. In fact, if this flag is
+<xref linkend="ref_guide_schema_info_list"/>. In fact, if this flag is
omitted, it defaults to the value of the <literal>Schemas</literal> property. If
the <literal>Schemas</literal> property is not defined, all schemas will be
reverse-mapped.
@@ -668,7 +668,7 @@
</literal>, or your favorite Java compiler. Make sure the classes and their
metadata are located in the directory corresponding to the <literal>-package
</literal> flag you gave the reverse mapping tool. Finally, enhance the classes
-if necessary (see <xref linkend="ref_guide_pc_enhance"></xref> ).
+if necessary (see <xref linkend="ref_guide_pc_enhance"/> ).
</para>
</listitem>
</orderedlist>
@@ -884,7 +884,7 @@
is up to you to define the mappings between these models. The mapping
tool's <literal>validate</literal> action is useful to meet-in-the-middle
mappers. We examined the mapping tool in
-<xref linkend="ref_guide_mapping_mappingtool"></xref>. The <literal>validate
+<xref linkend="ref_guide_mapping_mappingtool"/>. The <literal>validate
</literal> action verifies that the mapping information for a class matches the
class definition and the existing schema. It throws an informative exception
when your mappings are incorrect.
@@ -899,7 +899,7 @@
</example>
<para>
The <literal>buildSchema</literal> action we discussed in
-<xref linkend="ref_guide_mapping_mappingtool"></xref> is also somewhat useful
+<xref linkend="ref_guide_mapping_mappingtool"/> is also somewhat useful
during meet-in-the-middle mapping. Unlike the <literal>validate</literal>
action, which throws an exception if your mapping data does not match the
existing schema, the <literal>buildSchema</literal> action assumes your mapping
@@ -909,7 +909,7 @@
</para>
<para>
<literal>buildSchema</literal> is the default action when you use JPA mapping
-defaults ( <xref linkend="ref_guide_mapping_defaults"></xref> ).
+defaults ( <xref linkend="ref_guide_mapping_defaults"/> ).
</para>
<example id="ref_guide_mapping_middle_buildschema_mid">
<title>
@@ -955,14 +955,14 @@
OpenJPA relies on foreign key constraint information at runtime to order SQL
appropriately. Be sure to set your mapping defaults to reflect your existing
database constraints, or use explicit foreign key mappings as described in
-<phrase><xref linkend="ref_guide_mapping_jpa_fk"></xref></phrase>.
+<phrase><xref linkend="ref_guide_mapping_jpa_fk"/></phrase>.
</para>
</important>
<para>
The <link linkend="openjpa.jdbc.MappingDefaults"><literal>
openjpa.jdbc.MappingDefaults</literal></link> configuration property controls
the <classname>MappingDefaults</classname> interface implementation in use. This
-is a plugin property (see <xref linkend="ref_guide_conf_plugins"></xref> ), so
+is a plugin property (see <xref linkend="ref_guide_conf_plugins"/> ), so
you can substitute your own implementation or configure the existing ones.
OpenJPA includes the following standard implementations:
</para>
@@ -1005,7 +1005,7 @@
classes. You can specify a built-in strategy alias or the full class name of a
<link linkend="ref_guide_mapping_custom_class"> custom class strategy</link>.
You can also use OpenJPA's plugin format (see
-<xref linkend="ref_guide_conf_plugins"></xref>) to pass arguments to the
+<xref linkend="ref_guide_conf_plugins"/>) to pass arguments to the
strategy instance. See the
<ulink url="../apidocs/org/apache/openjpa/jdbc/meta/strats/package-summary.html">
<literal>org.apache.openjpa.jdbc.meta.strats</literal></ulink> package for
@@ -1018,7 +1018,7 @@
subclasses. You can specify a builtin strategy alias or the full class name of a
<link linkend="ref_guide_mapping_custom_class"> custom class strategy</link>.
You can also use OpenJPA's plugin format (see
-<xref linkend="ref_guide_conf_plugins"></xref>) to pass arguments to the
+<xref linkend="ref_guide_conf_plugins"/>) to pass arguments to the
strategy instance. Common strategies are <literal>vertical</literal> and
<literal>flat</literal>, the default. See the
<ulink url="../apidocs/org/apache/openjpa/jdbc/meta/strats/package-summary.html">
@@ -1032,7 +1032,7 @@
without a version field. You can specify a builtin strategy alias or the full
class name of a <link linkend="ref_guide_mapping_custom_versdiscrim"> custom
version strategy</link>. You can also use OpenJPA's plugin format (see
-<xref linkend="ref_guide_conf_plugins"></xref>) to pass arguments to the
+<xref linkend="ref_guide_conf_plugins"/>) to pass arguments to the
strategy instance. Common strategies are <literal>none</literal>, <literal>
state-comparison</literal>, <literal> timestamp</literal>, and <literal>
version-number</literal>, the default. See the
@@ -1048,7 +1048,7 @@
or the full class name of a
<link linkend="ref_guide_mapping_custom_versdiscrim"> custom discriminator
strategy</link>. You can also use OpenJPA's plugin format (see
-<xref linkend="ref_guide_conf_plugins"></xref>) to pass arguments to the
+<xref linkend="ref_guide_conf_plugins"/>) to pass arguments to the
strategy instance. Common strategies are <literal>final</literal> for a base
class without subclasses, <literal>none</literal> to use joins to subclass
tables rather than a discriminator column, and <literal> class-name</literal>,
@@ -1062,11 +1062,11 @@
<para>
<literal>FieldStrategies</literal>: This property associates field types with
custom strategies. The format of this property is similar to that of plugin
-strings (see <xref linkend="ref_guide_conf_plugins"></xref> ), without the class
+strings (see <xref linkend="ref_guide_conf_plugins"/> ), without the class
name. It is a comma-separated list of key/value pairs, where each key is a
possible field type, and each value is itself a plugin string describing the
strategy for that type. We present an example below. See
-<xref linkend="ref_guide_mapping_custom_field"></xref> for information on custum
+<xref linkend="ref_guide_mapping_custom_field"/> for information on custum
field strategies.
</para>
</listitem>
@@ -1128,7 +1128,7 @@
<para>
<literal>VersionColumnName</literal>: The default name of version columns. If
you use custom lock groups, this name may be combined with lock group names. See
-<xref linkend="ref_guide_lock_groups"></xref> for more information on lock
+<xref linkend="ref_guide_lock_groups"/> for more information on lock
groups.
</para>
</listitem>
@@ -1234,11 +1234,11 @@
<para>
In JPA, mapping metadata is defined in annotations. Future versions of the JPA
drafts will also define a mapping XML format.
-<xref linkend="jpa_overview_mapping"></xref> in the JPA Overview describes JPA
+<xref linkend="jpa_overview_mapping"/> in the JPA Overview describes JPA
mapping options.
</para>
<para>
-<xref linkend="ref_guide_meta_factory"></xref> introduced OpenJPA's <classname>
+<xref linkend="ref_guide_meta_factory"/> introduced OpenJPA's <classname>
MetaDataFactory</classname> interface. OpenJPA uses this same interface to
abstract the storage and retrieval of mapping information. OpenJPA includes the
built-in mapping factories below, and you can create your own factory if you
@@ -1288,7 +1288,7 @@
</secondary>
</indexterm>
<para>
-The JPA Overview's <xref linkend="jpa_overview_mapping"></xref> explains join
+The JPA Overview's <xref linkend="jpa_overview_mapping"/> explains join
mapping. All of the examples in that document, however, use "standard" joins, in
that there is one foreign key column for each primary key column in the target
table. OpenJPA supports additional join patterns, including partial primary key
@@ -1327,7 +1327,7 @@
org.apache.openjpa.jdbc.meta.Joinable</classname></ulink> interface. All built
in basic mappings implement this interface, including basic fields of embedded
objects. OpenJPA will also respect any custom mappings that implement this
-interface. See <xref linkend="ref_guide_mapping_custom"></xref> for an
+interface. See <xref linkend="ref_guide_mapping_custom"/> for an
examination of custom mappings.
</para>
<para>
@@ -1356,8 +1356,8 @@
<mediaobject>
<imageobject>
<!-- PNG image data, 427 x 211 (see README) -->
- <imagedata fileref="img/joins-constant.png" width="285px">
- </imagedata>
+ <imagedata fileref="img/joins-constant.png" width="285px"/>
+
</imageobject>
</mediaobject>
<para>
@@ -1440,7 +1440,7 @@
</indexterm>
<para>
OpenJPA supports many persistence strategies beyond those of the JPA
-specification. <xref linkend="ref_guide_meta_jpa"></xref> covered the logical
+specification. <xref linkend="ref_guide_meta_jpa"/> covered the logical
metadata for OpenJPA's additional persistence strategies. We now demonstrate how
to map entities using these strategies to the database.
</para>
@@ -1481,7 +1481,7 @@
</primary>
</indexterm>
<para>
-<xref linkend="ref_guide_pc_oid"></xref> describes how to use datastore identity
+<xref linkend="ref_guide_pc_oid"/> describes how to use datastore identity
in JPA. OpenJPA requires a single numeric primary key column to hold datastore
identity values. The
<ulink url="../apidocs/org/apache/openjpa/persistence/jdbc/DataStoreIdColumn.html">
@@ -1519,7 +1519,7 @@
<para>
All properties correspond exactly to the same-named properties on the standard
<classname>Column</classname> annotation, described in
-<xref linkend="jpa_overview_mapping_column"></xref>.
+<xref linkend="jpa_overview_mapping_column"/>.
</para>
<example id="ref_guide_mapping_jpa_datastoreidex">
<title>
@@ -1637,16 +1637,16 @@
<para>
The <literal>lockGroup</literal> property allows you to specify that a version
column is for some lock group other than the default group. See
-<xref linkend="ref_guide_lock_groups"></xref> for an example. All other
+<xref linkend="ref_guide_lock_groups"/> for an example. All other
properties correspond exactly to the same-named properties on the standard
<classname>Column</classname> annotation, described in
-<xref linkend="jpa_overview_mapping_column"></xref>.
+<xref linkend="jpa_overview_mapping_column"/>.
</para>
<para>
By default, OpenJPA assumes that surrogate versioning uses a version number
strategy. You can choose a different strategy with the <classname>
VersionStrategy</classname> annotation described in
-<xref linkend="version-strategy"></xref>.
+<xref linkend="version-strategy"/>.
</para>
</section>
<section id="ref_guide_mapping_jpa_columns">
@@ -1686,13 +1686,13 @@
<ulink url="../apidocs/org/apache/openjpa/persistence/jdbc/Columns.html">
<classname>org.apache.openjpa.persistence.jdbc.Columns</classname></ulink>
annotation, which contains an array of <classname>Column</classname> values.
-<xref linkend="ref_guide_mapping_custom_field_conf_extex"></xref> uses OpenJPA's
+<xref linkend="ref_guide_mapping_custom_field_conf_extex"/> uses OpenJPA's
<classname>Columns</classname> annotation to map a <classname>java.awt.Point
</classname> to separate X and Y columns.
</para>
<para>
Remember to annotate custom field types with <classname> Persistent</classname>
-, as described in <xref linkend="ref_guide_meta_jpa_persistent"></xref>.
+, as described in <xref linkend="ref_guide_meta_jpa_persistent"/>.
</para>
</section>
<section id="ref_guide_mapping_jpa_fieldjoin">
@@ -1700,7 +1700,7 @@
Join Column Attribute Targets
</title>
<para>
-<xref linkend="jpa_overview_mapping_rel"></xref> in the JPA Overview introduced
+<xref linkend="jpa_overview_mapping_rel"/> in the JPA Overview introduced
you to the <classname>JoinColumn</classname> annotation. A <classname>
JoinColumn</classname>'s <literal> referencedColumnName</literal> property
declares which column in the table of the related type this join column links
@@ -1738,7 +1738,7 @@
<para>
JPA uses the <classname>AttributeOverride</classname> annotation to override the
default mappings of an embeddable class. The JPA Overview details this process
-in <xref linkend="jpa_overview_mapping_embed"></xref>. <classname>
+in <xref linkend="jpa_overview_mapping_embed"/>. <classname>
AttributeOverride</classname>s suffice for simple mappings, but do not allow
you to override complex mappings. Also, JPA has no way to differentitate between
a null embedded object and one with default values for all of its fields.
@@ -1822,36 +1822,36 @@
<para>
<literal>ContainerTable containerTable</literal>: Table for the new collection
or map field mapping. We cover collection mappings in
-<xref linkend="ref_guide_mapping_jpa_coll"></xref>, and map mappings in
-<xref linkend="ref_guide_mapping_jpa_map"></xref>.
+<xref linkend="ref_guide_mapping_jpa_coll"/>, and map mappings in
+<xref linkend="ref_guide_mapping_jpa_map"/>.
</para>
</listitem>
<listitem>
<para>
<literal>ElementColumn[] elementColumns</literal>: Element columns for the new
collection or map field mapping. You will see how to use element columns in
-<xref linkend="ref_guide_mapping_jpa_coll_cols"></xref>.
+<xref linkend="ref_guide_mapping_jpa_coll_cols"/>.
</para>
</listitem>
<listitem>
<para>
<literal>ElementJoinColumn[] elementJoinColumns</literal>: Element join columns
for the new collection or map field mapping. You will see how to use element
-join columns in <xref linkend="ref_guide_mapping_jpa_coll_joincols"></xref>.
+join columns in <xref linkend="ref_guide_mapping_jpa_coll_joincols"/>.
</para>
</listitem>
<listitem>
<para>
<literal>KeyColumn[] keyColumns</literal>: Map key columns for the new map
field mapping. You will see how to use key columns in
-<xref linkend="ref_guide_mapping_jpa_map_keycols"></xref>.
+<xref linkend="ref_guide_mapping_jpa_map_keycols"/>.
</para>
</listitem>
<listitem>
<para>
<literal>KeyJoinColumn[] keyJoinColumns</literal>: Key join columns for the new
map field mapping. You will see how to use key join columns in
-<xref linkend="ref_guide_mapping_jpa_map_keyjoincols"></xref>.
+<xref linkend="ref_guide_mapping_jpa_map_keyjoincols"/>.
</para>
</listitem>
</itemizedlist>
@@ -1915,7 +1915,7 @@
</secondary>
</indexterm>
<para>
-In <xref linkend="ref_guide_meta_jpa_persistent_coll"></xref>, we explored the
+In <xref linkend="ref_guide_meta_jpa_persistent_coll"/>, we explored the
<classname>PersistentCollection</classname> annotation for persistent collection
fields that aren't a standard <literal>OneToMany</literal> or <literal>
ManyToMany</literal> relation. To map these non-standard collections, combine
@@ -1980,7 +1980,7 @@
</literal>, and <literal>joinColumns</literal> properties describe the container
table and how it joins to the owning entity's table. These properties correspond
to the same-named properties on the standard <classname> JoinTable</classname>
-annotation, described in <xref linkend="jpa_overview_mapping_assoccoll"></xref>
+annotation, described in <xref linkend="jpa_overview_mapping_assoccoll"/>
. If left unspecified, the name of the table defaults to the first five
characters of the entity table name, plus an underscore, plus the field name.
The <literal>joinForeignKey</literal> and <literal> joinIndex</literal>
@@ -2022,7 +2022,7 @@
it does not have the <literal> table</literal> property of a standard
<classname> Column</classname>. Otherwise, the <classname>ElementColumn
</classname> and standard <classname>Column</classname> annotations are
-equivalent. See <xref linkend="jpa_overview_mapping_column"></xref> in the JPA
+equivalent. See <xref linkend="jpa_overview_mapping_column"/> in the JPA
Overview for a review of the <classname>Column</classname> annotation.
</para>
</section>
@@ -2057,7 +2057,7 @@
above, <classname> ElementJoinColumn</classname>s can reference a linked
attribute rather than a static linked column. Otherwise, the <classname>
ElementJoinColumn</classname> and standard <classname>JoinColumn</classname>
-annotations are equivalent. See <xref linkend="jpa_overview_mapping_rel"></xref>
+annotations are equivalent. See <xref linkend="jpa_overview_mapping_rel"/>
in the JPA Overview for a review of the <classname>JoinColumn</classname>
annotation.
</para>
@@ -2144,7 +2144,7 @@
the <literal>enabled</literal> property to <literal>false</literal>. All other
properties correspond exactly to the same-named properties on the standard
<classname>Column</classname> annotation, described in
-<xref linkend="jpa_overview_mapping_column"></xref>.
+<xref linkend="jpa_overview_mapping_column"/>.
</para>
</section>
<section id="ref_guide_mapping_jpa_coll_ex">
@@ -2154,8 +2154,8 @@
<mediaobject>
<imageobject>
<!-- PNG image data, 383 x 176 (see README) -->
- <imagedata fileref="img/basic-coll.png" width="255px">
- </imagedata>
+ <imagedata fileref="img/basic-coll.png" width="255px"/>
+
</imageobject>
</mediaobject>
<para>
@@ -2198,8 +2198,8 @@
<mediaobject>
<imageobject>
<!-- PNG image data, 545 x 239 (see README) -->
- <imagedata fileref="img/embedded-coll.png" width="363px">
- </imagedata>
+ <imagedata fileref="img/embedded-coll.png" width="363px"/>
+
</imageobject>
</mediaobject>
<example id="ref_guide_mapping_jpa_coll_embedex">
@@ -2259,15 +2259,15 @@
Standard JPA supports <classname>OneToMany</classname> fields without a
<literal>mappedBy</literal> inverse, but only by mapping these fields to a
<classname>JoinTable</classname> (see
-<xref linkend="jpa_overview_mapping_assoccoll"></xref> in the JPA Overview for
+<xref linkend="jpa_overview_mapping_assoccoll"/> in the JPA Overview for
details). Often, you'd like to create a one-many association based on an inverse
foreign key (logical or actual) in the table of the related type.
</para>
<mediaobject>
<imageobject>
<!-- PNG image data, 392 x 192 (see README) -->
- <imagedata fileref="img/inv-key-coll.png" width="261">
- </imagedata>
+ <imagedata fileref="img/inv-key-coll.png" width="261"/>
+
</imageobject>
</mediaobject>
<para>
@@ -2326,7 +2326,7 @@
</secondary>
</indexterm>
<para>
-<xref linkend="ref_guide_meta_jpa_persistent_map"></xref> discussed the
+<xref linkend="ref_guide_meta_jpa_persistent_map"/> discussed the
<classname>PersistentMap</classname> annotation for persistent map fields. To
map these non-standard fields to the database, combine OpenJPA's <classname>
ContainerTable</classname> annotation with <classname>KeyColumn</classname> s,
@@ -2337,11 +2337,11 @@
</para>
<para>
We detailed the <literal>ContainerTable</literal> annotation in
-<xref linkend="ref_guide_mapping_jpa_coll_table"></xref>. We also discussed
+<xref linkend="ref_guide_mapping_jpa_coll_table"/>. We also discussed
element columns, join columns, and embedded mappings in
-<xref linkend="ref_guide_mapping_jpa_coll_cols"></xref>,
-<xref linkend="ref_guide_mapping_jpa_coll_joincols"></xref>, and
-<xref linkend="ref_guide_mapping_jpa_coll_embed"></xref>. Key columns, join
+<xref linkend="ref_guide_mapping_jpa_coll_cols"/>,
+<xref linkend="ref_guide_mapping_jpa_coll_joincols"/>, and
+<xref linkend="ref_guide_mapping_jpa_coll_embed"/>. Key columns, join
columns, and embedded mappings are new, however; we tackle them below.
</para>
<section id="ref_guide_mapping_jpa_map_keycols">
@@ -2358,7 +2358,7 @@
</indexterm>
<para>
Key columns serve the same role for map keys as the element columns described in
-<xref linkend="ref_guide_mapping_jpa_coll_cols"></xref> serve for collection
+<xref linkend="ref_guide_mapping_jpa_coll_cols"/> serve for collection
elements. OpenJPA's
<ulink url="../apidocs/org/apache/openjpa/persistence/jdbc/KeyColumn.html">
<classname>org.apache.openjpa.persistence.jdbc.KeyColumn</classname></ulink>
@@ -2372,7 +2372,7 @@
does not have the <literal> table</literal> property of a standard <classname>
Column</classname>. Otherwise, the <classname>KeyColumn</classname> and standard
<classname>Column</classname> annotations are equivalent. See
-<xref linkend="jpa_overview_mapping_column"></xref> in the JPA Overview for a
+<xref linkend="jpa_overview_mapping_column"/> in the JPA Overview for a
review of the <classname>Column</classname> annotation.
</para>
</section>
@@ -2407,7 +2407,7 @@
above, <classname> KeyJoinColumn</classname>s can reference a linked field
rather than a static linked column. Otherwise, the <classname> KeyJoinColumn
</classname> and standard <classname>JoinColumn</classname> annotations are
-equivalent. See <xref linkend="jpa_overview_mapping_rel"></xref> in the JPA
+equivalent. See <xref linkend="jpa_overview_mapping_rel"/> in the JPA
Overview for a review of the <classname>JoinColumn</classname> annotation.
</para>
</section>
@@ -2440,8 +2440,8 @@
<mediaobject>
<imageobject>
<!-- PNG image data, 410 x 266 (see README) -->
- <imagedata fileref="img/string-rel-map.png" width="273px">
- </imagedata>
+ <imagedata fileref="img/string-rel-map.png" width="273px"/>
+
</imageobject>
</mediaobject>
<para>
@@ -2500,8 +2500,8 @@
</para>
<para>
OpenJPA assumes certain columns have indexes or constraints based on your
-mapping defaults, as detailed in <xref linkend="ref_guide_mapping_defaults">
-</xref>. You can override the configured defaults on individual joins, field
+mapping defaults, as detailed in <xref linkend="ref_guide_mapping_defaults"/>
+. You can override the configured defaults on individual joins, field
values, collection elements, map keys, or map values using the annotations
presented in the following sections.
</para>
@@ -2696,14 +2696,14 @@
Examples
</title>
<para>
-Here again is our map example from <xref linkend="ref_guide_mapping_jpa_map">
-</xref>, now with explicit indexes and constraints added.
+Here again is our map example from <xref linkend="ref_guide_mapping_jpa_map"/>
+, now with explicit indexes and constraints added.
</para>
<mediaobject>
<imageobject>
<!-- PNG image data, 410 x 266 (see README) -->
- <imagedata fileref="img/string-rel-map.png" width="273px">
- </imagedata>
+ <imagedata fileref="img/string-rel-map.png" width="273px"/>
+
</imageobject>
</mediaobject>
<example id="ref_guide_mapping_jpa_constraintex_map">
@@ -2804,7 +2804,7 @@
<listitem>
<para>
Table-per-class hierarchies impose limitations on eager fetching. See
-<xref linkend="ref_guide_perfpack_eager_consider"></xref>.
+<xref linkend="ref_guide_perfpack_eager_consider"/>.
</para>
</listitem>
</itemizedlist>
@@ -2812,7 +2812,7 @@
<para>
Non-polymorphic relations do not suffer from these limitations. You can declare
a non-polymorphic relation using the extensions described in
-<xref linkend="nonpolymorphic"></xref>.
+<xref linkend="nonpolymorphic"/>.
</para>
</note>
</section>
@@ -2863,8 +2863,8 @@
<ulink url="../apidocs/org/apache/openjpa/persistence/jdbc/EagerFetchType.html">
<classname>org.apache.openjpa.persistence.jdbc.EagerFetchType</classname>
</ulink> enum: <literal>JOIN</literal>, <literal>PARALLEL</literal>, or
-<literal>NONE</literal>.</phrase> See <xref linkend="ref_guide_perfpack_eager">
-</xref> for a discussion of eager fetching.
+<literal>NONE</literal>.</phrase> See <xref linkend="ref_guide_perfpack_eager"/>
+ for a discussion of eager fetching.
</para>
</section>
<section id="class-strategy">
@@ -2889,7 +2889,7 @@
The <ulink url="../apidocs/org/apache/openjpa/persistence/jdbc/Strategy.html">
<classname>org.apache.openjpa.persistence.jdbc.Strategy</classname></ulink>
class annotation allows you to specify a custom mapping strategy for your class.
-See <xref linkend="ref_guide_mapping_custom"></xref> for information on custom
+See <xref linkend="ref_guide_mapping_custom"/> for information on custom
mappings.
</para>
</section>
@@ -2916,7 +2916,7 @@
<ulink url="../apidocs/org/apache/openjpa/persistence/jdbc/DiscriminatorStrategy.html">
<classname>org.apache.openjpa.persistence.jdbc.DiscriminatorStrategy</classname>
</ulink> class annotation allows you to specify a custom discriminator strategy.
-See <xref linkend="ref_guide_mapping_custom"></xref> for information on custom
+See <xref linkend="ref_guide_mapping_custom"/> for information on custom
mappings.
</para>
</section>
@@ -2943,7 +2943,7 @@
<ulink url="../apidocs/org/apache/openjpa/persistence/jdbc/VersionStrategy.html">
<classname>org.apache.openjpa.persistence.jdbc.VersionStrategy</classname>
</ulink> class annotation allows you to specify a custom version strategy. See
-<xref linkend="ref_guide_mapping_custom"></xref> for information on custom
+<xref linkend="ref_guide_mapping_custom"/> for information on custom
mappings.
</para>
</section>
@@ -2983,8 +2983,8 @@
<ulink url="../apidocs/org/apache/openjpa/persistence/jdbc/EagerFetchType.html">
<classname>org.apache.openjpa.persistence.jdbc.EagerFetchType</classname>
</ulink> enum: <literal>JOIN</literal>, <literal>PARALLEL</literal>, or
-<literal>NONE</literal>.</phrase> See <xref linkend="ref_guide_perfpack_eager">
-</xref> for a discussion of eager fetching.
+<literal>NONE</literal>.</phrase> See <xref linkend="ref_guide_perfpack_eager"/>
+ for a discussion of eager fetching.
</para>
</section>
<section id="nonpolymorphic">
@@ -3014,7 +3014,7 @@
<note>
<para>
OpenJPA also includes the <literal>type</literal> metadata extension for
-narrowing the declared type of a field See <xref linkend="type"></xref>.
+narrowing the declared type of a field See <xref linkend="type"/>.
</para>
</note>
<para>
@@ -3140,7 +3140,7 @@
<para>
OpenJPA's family of strategy extensions allow you to specify a custom mapping
strategy or value handler for a field. See
-<xref linkend="ref_guide_mapping_custom"></xref> for information on custom
+<xref linkend="ref_guide_mapping_custom"/> for information on custom
mappings.
</para>
<para>
@@ -3241,8 +3241,8 @@
annotation allows you to declare a custom class mapping strategy in JPA mapping
metadata. Set the value of the annotation to the full class name of your custom
strategy.</phrase> You can configure your strategy class' bean properties using
-OpenJPA's plugin syntax, detailed in <xref linkend="ref_guide_conf_plugins">
-</xref>.
+OpenJPA's plugin syntax, detailed in <xref linkend="ref_guide_conf_plugins"/>
+.
</para>
</section>
<section id="ref_guide_mapping_custom_versdiscrim">
@@ -3275,7 +3275,7 @@
<para>
As with custom class mappings, you can configure your strategy class' bean
properties using OpenJPA's plugin syntax, detailed in
-<xref linkend="ref_guide_conf_plugins"></xref>.
+<xref linkend="ref_guide_conf_plugins"/>.
</para>
</section>
<section id="ref_guide_mapping_custom_field">
@@ -3380,7 +3380,7 @@
will automatically use your custom strategies when it encounters a field of the
associated type. OpenJPA will use your custom value handlers whenever it
encounters a field, collection element, map key, or map value of the associated
-type. <xref linkend="ref_guide_mapping_defaults"></xref> described mapping
+type. <xref linkend="ref_guide_mapping_defaults"/> described mapping
defaults in detail.
</para>
<para>
@@ -3396,7 +3396,7 @@
<classname>org.apache.openjpa.persistence.jdbc.KeyStrategy</classname></ulink>
annotations.</phrase> You can configure the named strategy or handler's bean
properties in these extensions using OpenJPA's plugin format (see
-<xref linkend="ref_guide_conf_plugins"></xref> ).
+<xref linkend="ref_guide_conf_plugins"/> ).
</para>
<para>
The example below installs a custom strategy on the <literal>coverImage
@@ -3469,7 +3469,7 @@
OpenJPA's <link linkend="openjpa.OrphanedKeyAction"><literal>
openjpa.OrphanedKeyAction</literal></link> configuration property controls what
action to take when OpenJPA encounters an orphaned key. You can set this plugin
-string (see <xref linkend="ref_guide_conf_plugins"></xref>) to a custom
+string (see <xref linkend="ref_guide_conf_plugins"/>) to a custom
implementation of the
<ulink url="../apidocs/org/apache/openjpa/event/OrphanedKeyAction.html">
<classname> org.apache.openjpa.event.OrphanedKeyAction</classname></ulink>