openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mprud...@apache.org
Subject svn commit: r440450 [3/3] - /incubator/openjpa/trunk/openjpa-project/src/doc/manual/
Date Tue, 05 Sep 2006 19:28:38 GMT
Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml Tue Sep  5 12:28:36
2006
@@ -3,8 +3,8 @@
         Metadata
     </title>
     <para>
-The JPA Overview covers JPA metadata in <xref linkend="jpa_overview_meta">
-</xref>. This chapter discusses OpenJPA's extensions to standard JPA metadata.
+The JPA Overview covers JPA metadata in <xref linkend="jpa_overview_meta"/>
+. This chapter discusses OpenJPA's extensions to standard JPA metadata.
     </para>
     <section id="ref_guide_meta_factory">
         <title>
@@ -24,14 +24,14 @@
         <para>
 The <link linkend="openjpa.MetaDataFactory"><literal>openjpa.MetaDataFactory
 </literal></link> configuration property controls metadata loading and storing.
-This property takes a plugin string (see <xref linkend="ref_guide_conf_plugins">
-</xref>) describing a concrete
+This property takes a plugin string (see <xref linkend="ref_guide_conf_plugins"/>
+) describing a concrete
 <ulink url="../apidocs/org/apache/openjpa/meta/MetaDataFactory.html">
 <classname>org.apache.openjpa.meta.MetaDataFactory</classname></ulink>
 implementation. A metadata factory can load mapping information as well as
 persistence metadata, or it can leave mapping information to a separate
 <emphasis>mapping factory</emphasis> (see
-<xref linkend="ref_guide_mapping_factory"></xref> ). OpenJPA recognizes the
+<xref linkend="ref_guide_mapping_factory"/> ). OpenJPA recognizes the
 following built-in metadata factories:
         </para>
         <itemizedlist>
@@ -48,7 +48,7 @@
 The standard metadata factories all accept the following properties for locating
 persistent classes. Each property represents a different mechanism for locating
 persistent types; you can choose the mechanism or combination of mechanisms that
-are most convenient. See <xref linkend="ref_guide_pc_pcclasses"></xref> for a
+are most convenient. See <xref linkend="ref_guide_pc_pcclasses"/> for a
 discussion of when it is necessary to list your persistent classes.
         </para>
         <itemizedlist>
@@ -112,8 +112,8 @@
         <para>
 This section describes OpenJPA's core additions to standard entity metadata. We
 present the object-relational mapping syntax to support these additions in
-<xref linkend="ref_guide_mapping_jpa"></xref>. Finally,
-<xref linkend="ref_guide_meta_ext"></xref> covers additional extensions to JPA
+<xref linkend="ref_guide_mapping_jpa"/>. Finally,
+<xref linkend="ref_guide_meta_ext"/> covers additional extensions to JPA
 metadata that allow you to access auxiliary OpenJPA features.
         </para>
         <section id="ref_guide_meta_jpa_datastoreid">
@@ -133,9 +133,9 @@
 to act as primary keys. OpenJPA, however, can create and maintain a surrogate
 primary key value when you do not declare any <literal>Id</literal> fields. This
 form of persistent identity is called <emphasis>datastore identity</emphasis>.
-<xref linkend="ref_guide_pc_oid"></xref> discusses OpenJPA's support for
+<xref linkend="ref_guide_pc_oid"/> discusses OpenJPA's support for
 datastore identity in JPA. We cover how to map your datastore identity primary
-key column in <xref linkend="ref_guide_mapping_jpa_datastoreid"></xref>
+key column in <xref linkend="ref_guide_mapping_jpa_datastoreid"/>
             </para>
         </section>
         <section id="ref_guide_meta_jpa_version">
@@ -154,7 +154,7 @@
 Just as OpenJPA can maintain your entity's identity without any <literal>Id
 </literal> fields, OpenJPA can maintain your entity's optimistic version without
 any <literal>Version</literal> fields.
-<xref linkend="ref_guide_mapping_jpa_version"></xref> shows you how to map
+<xref linkend="ref_guide_mapping_jpa_version"/> shows you how to map
 surrogate version columns.
             </para>
         </section>
@@ -222,8 +222,8 @@
 Though you can use the <classname>Persistent</classname> annotation in place
of
 most of the standard direct field annotations mentioned above, we recommend
 primarily using it for non-standard and custom types for which no standard JPA
-annotation exists. For example, <xref linkend="ref_guide_mapping_jpa_columns">
-</xref> demonstrates the use of the <classname>Persistent</classname> annotation
+annotation exists. For example, <xref linkend="ref_guide_mapping_jpa_columns"/>
+ demonstrates the use of the <classname>Persistent</classname> annotation
 to denote a persistent <classname>java.awt.Point</classname> field.
             </para>
         </section>
@@ -295,7 +295,7 @@
                 </listitem>
             </itemizedlist>
             <para>
-<xref linkend="ref_guide_mapping_jpa_coll"></xref> contains several examples
of
+<xref linkend="ref_guide_mapping_jpa_coll"/> contains several examples of
 using <classname>PersistentCollection</classname> to mark non-standard
 collection fields persistent.
             </para>
@@ -376,7 +376,7 @@
             <para>
 Map keys and values in OpenJPA can be entities, simple types (primitive
 wrappers, <classname>String</classname> s, etc), custom types, or embedded
-objects. <xref linkend="ref_guide_mapping_jpa_map"></xref> contains several
+objects. <xref linkend="ref_guide_mapping_jpa_map"/> contains several
 examples of using <classname>PersistentMap</classname> to annotate persistent
 map fields.
             </para>
@@ -397,7 +397,7 @@
         <para>
 OpenJPA extends standard metadata to allow you to access advanced OpenJPA
 functionality. This section covers persistence metadata extensions; we discuss
-mapping metadata extensions in <xref linkend="ref_guide_mapping_ext"></xref>.
+mapping metadata extensions in <xref linkend="ref_guide_mapping_ext"/>.
 All metadata extensions are optional; OpenJPA will rely on its defaults when no
 explicit data is provided.
         </para>
@@ -432,8 +432,8 @@
 <ulink url="../apidocs/org/apache/openjpa/persistence/FetchGroup.html">
 <classname>org.apache.openjpa.persistence.FetchGroup</classname></ulink>
 annotations allow you to define fetch groups in your JPA entities.
-<xref linkend="ref_guide_fetch"></xref> discusses OpenJPA's support for fetch
-groups in general; see <xref linkend="ref_guide_fetch_custom"></xref> for how
to
+<xref linkend="ref_guide_fetch"/> discusses OpenJPA's support for fetch
+groups in general; see <xref linkend="ref_guide_fetch_custom"/> for how to
 use these annotations in particular.
                 </para>
             </section>
@@ -456,7 +456,7 @@
                     </seealso>
                 </indexterm>
                 <para>
-<xref linkend="ref_guide_cache"></xref> examines caching in OpenJPA. Metadata
+<xref linkend="ref_guide_cache"/> examines caching in OpenJPA. Metadata
 extensions allow individual classes to override system caching defaults.
                 </para>
                 <para>
@@ -540,7 +540,7 @@
                 <para>
 The OpenJPA <link linkend="ref_guide_pc_enhance">enhancer</link> may add a
 synthetic field to detachable classes to hold detached state (see
-<xref linkend="ref_guide_detach_graph"></xref> for details). You can instead
+<xref linkend="ref_guide_detach_graph"/> for details). You can instead
 declare your own detached state field or supress the creation of a detached
 state field altogether. In the latter case, your class must not use
 <link linkend="ref_guide_pc_oid">datastore identity</link>, and should declare
@@ -590,7 +590,7 @@
 <ulink url="../apidocs/org/apache/openjpa/persistence/LockGroups.html">
 <classname>org.apache.openjpa.persistence.LockGroups</classname></ulink>
 annotation accepts an array of lock group names.</phrase> For details on lock
-groups, see <xref linkend="ref_guide_lock_groups_and_subclasses"></xref>.
+groups, see <xref linkend="ref_guide_lock_groups_and_subclasses"/>.
                 </para>
             </section>
             <section id="auditable">
@@ -688,7 +688,7 @@
 org.apache.openjpa.persistence.LRS</classname></ulink> annotation,</phrase>
 indicates that a field should use OpenJPA's special large result set collection
 or map proxies. A complete description of large result set proxies is available
-in <xref linkend="ref_guide_pc_scos_proxy_lrs"></xref>.
+in <xref linkend="ref_guide_pc_scos_proxy_lrs"/>.
                 </para>
             </section>
             <section id="order-by">
@@ -707,7 +707,7 @@
                     </tertiary>
                 </indexterm>
                 <para>
-<phrase> The JPA Overview's <xref linkend="jpa_overview_meta_orderby"></xref>
+<phrase> The JPA Overview's <xref linkend="jpa_overview_meta_orderby"/>
 describes JPA's <literal>OrderBy</literal> annotation for loading the elements
 of collection fields in a prescribed order.</phrase> Ordering syntax is as
 follows:
@@ -775,7 +775,7 @@
 <ulink url="../apidocs/org/apache/openjpa/persistence/InverseLogical.html">
 <classname>org.apache.openjpa.persistence.InverseLogical</classname></ulink>
 annotation.</phrase> We discuss logical bidirectional relations and this
-extension in detail in <xref linkend="ref_guide_inverses"></xref>.
+extension in detail in <xref linkend="ref_guide_inverses"/>.
                 </para>
             </section>
             <section id="lock-group">
@@ -802,8 +802,8 @@
 <classname>org.apache.openjpa.persistence.LockGroup</classname></ulink>
 annotation</phrase> to name the lock group for a field. You can exclude a field
 from optimistic locking with a value of <literal>none</literal>. We discuss
-lock groups and this extension further in <xref linkend="ref_guide_lock_groups">
-</xref>.
+lock groups and this extension further in <xref linkend="ref_guide_lock_groups"/>
+.
                 </para>
             </section>
             <section id="read-only">
@@ -930,7 +930,7 @@
                 </para>
                 <para>
 This extension is also used with OpenJPA's externalization feature, described in
-<xref linkend="ref_guide_pc_extern"></xref>.
+<xref linkend="ref_guide_pc_extern"/>.
                 </para>
                 <para>
 OpenJPA defines the following type annotations for field values, collection,
@@ -980,7 +980,7 @@
 <ulink url="../apidocs/org/apache/openjpa/persistence/Externalizer.html">
 <classname>org.apache.openjpa.persistence.Externalizer</classname></ulink>
 annotation</phrase> names a method to transform a field value into a value of
-another type. See <xref linkend="ref_guide_pc_extern"></xref> for details.
+another type. See <xref linkend="ref_guide_pc_extern"/> for details.
                 </para>
             </section>
             <section id="factory">
@@ -1006,7 +1006,7 @@
 <ulink url="../apidocs/org/apache/openjpa/persistence/Factory.html"><classname>
 org.apache.openjpa.persistence.Factory</classname></ulink> annotation</phrase>
 names a method to re-create a field value from its externalized form. See
-<xref linkend="ref_guide_pc_extern"></xref> for details.
+<xref linkend="ref_guide_pc_extern"/> for details.
                 </para>
             </section>
             <section id="external-values">
@@ -1033,7 +1033,7 @@
 <classname>org.apache.openjpa.persistence.ExternalValues</classname></ulink>
 annotation</phrase> declares values for transformation of simple fields to
 different constant values in the datastore. See
-<xref linkend="ref_guide_pc_extern_values"></xref> for details.
+<xref linkend="ref_guide_pc_extern_values"/> for details.
                 </para>
             </section>
         </section>

Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_optimization.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_optimization.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_optimization.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_optimization.xml Tue
Sep  5 12:28:36 2006
@@ -36,10 +36,10 @@
             Optimization Guidelines
         </title>
         <tgroup cols="2" align="left" colsep="1" rowsep="1">
-            <colspec colname="name">
-            </colspec>
-            <colspec colname="desc" colwidth="4*">
-            </colspec>
+            <colspec colname="name"/>
+            
+            <colspec colname="desc" colwidth="4*"/>
+            
             <tbody valign="top">
                 <row>
                     <entry colname="name">
@@ -533,7 +533,7 @@
 Attaching and even persisting instances can be more efficient when your detached
 objects use detached state managers. By default, OpenJPA does not use detached
 state managers when serializing an instance across tiers. See
-<xref linkend="ref_guide_detach_graph"></xref> for how to force OpenJPA to use
+<xref linkend="ref_guide_detach_graph"/> for how to force OpenJPA to use
 detached state managers across tiers, and for other options for more efficient
 attachment.
                         </para>

Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_pc.xml Tue Sep  5 12:28:36
2006
@@ -8,7 +8,7 @@
         </primary>
     </indexterm>
     <para>
-Persistent class basics are covered in <xref linkend="jpa_overview_pc"></xref>
+Persistent class basics are covered in <xref linkend="jpa_overview_pc"/>
 of the JPA Overview. This chapter details the persistent class features OpenJPA
 offers beyond the core JPA specification.
     </para>
@@ -57,7 +57,7 @@
             <listitem>
                 <para>
 If you configure OpenJPA to create the needed database schema on startup (see
-<xref linkend="ref_guide_mapping_synch"></xref> ), OpenJPA must know all of your
+<xref linkend="ref_guide_mapping_synch"/> ), OpenJPA must know all of your
 persistent classes up-front.
                 </para>
             </listitem>
@@ -66,7 +66,7 @@
 When any of these conditions are a factor in your JPA application, use the
 <literal>class</literal>, <literal> mapping-file</literal>, and <literal>
 jar-file</literal> elements of JPA's standard XML format to list your persistent
-classes. See <xref linkend="jpa_overview_persistence_xml"></xref> for details.
+classes. See <xref linkend="jpa_overview_persistence_xml"/> for details.
         </para>
         <note>
             <para>
@@ -113,8 +113,8 @@
         <mediaobject>
             <imageobject>
                 <!-- PNG image data, 509 x 133 (see README) -->
-                <imagedata fileref="img/enhancement.png" width="339px">
-                </imagedata>
+                <imagedata fileref="img/enhancement.png" width="339px"/>
+                
             </imageobject>
         </mediaobject>
         <para>
@@ -144,8 +144,8 @@
             </para>
             <note>
                 <para>
-You can also enhance via Ant; see <xref linkend="ref_guide_integration_enhance">
-</xref>.
+You can also enhance via Ant; see <xref linkend="ref_guide_integration_enhance"/>
+.
                 </para>
             </note>
             <example id="ref_guide_pc_enhance_enhancer">
@@ -158,7 +158,7 @@
             </example>
             <para>
 The enhancer accepts the standard set of command-line arguments defined by the
-configuration framework (see <xref linkend="ref_guide_conf_devtools"></xref>
),
+configuration framework (see <xref linkend="ref_guide_conf_devtools"/> ),
 along with the following flags:
             </para>
             <itemizedlist>
@@ -218,8 +218,8 @@
             </itemizedlist>
             <para>
 If you do not supply any arguments to the enhancer, it will run on the classes
-in your persistent class list (see <xref linkend="ref_guide_pc_pcclasses">
-</xref> ).
+in your persistent class list (see <xref linkend="ref_guide_pc_pcclasses"/>
+ ).
             </para>
             <para>
 You can run the enhancer over classes that have already been enhanced, in which
@@ -296,8 +296,8 @@
             <para>
 Searching for metadata for every class loaded by the JVM can slow application
 initialization. One way to speed things up is to take advantage of the optional
-persistent class list described in <xref linkend="ref_guide_pc_pcclasses">
-</xref>. If you declare a persistent class list, OpenJPA will only search for
+persistent class list described in <xref linkend="ref_guide_pc_pcclasses"/>
+. If you declare a persistent class list, OpenJPA will only search for
 metadata for classes in that list.
             </para>
             <para>
@@ -315,12 +315,12 @@
             </example>
             <para>
 You can pass settings to the agent using OpenJPA's plugin syntax (see
-<xref linkend="ref_guide_conf_plugins"></xref> ). The agent accepts the long
+<xref linkend="ref_guide_conf_plugins"/> ). The agent accepts the long
 form of any of the standard configuration options (
-<xref linkend="ref_guide_conf_devtools"></xref> ). It also accepts the following
+<xref linkend="ref_guide_conf_devtools"/> ). It also accepts the following
 options, the first three of which correspond exactly to to the same-named
 options of the enhancer tool described in
-<xref linkend="ref_guide_pc_enhance_build"></xref>:
+<xref linkend="ref_guide_pc_enhance_build"/>:
             </para>
             <itemizedlist>
                 <listitem>
@@ -386,7 +386,7 @@
 between a server using OpenJPA and a client that does not have access to
 enhanced classes or OpenJPA libraries. In some cases, however, you can make the
 persist and attach processes more robust and efficient by allowing breaks in
-serialization compatibility. See <xref linkend="ref_guide_detach_graph"></xref>
+serialization compatibility. See <xref linkend="ref_guide_detach_graph"/>
 for details.
             </para>
         </section>
@@ -416,12 +416,12 @@
 annotation. This annotation has <literal>strategy</literal> and <literal>
 generator</literal> properties that mirror the same-named properties on the
 standard <classname>javax.persistence.GeneratedValue</classname> annotation
-described in <xref linkend="jpa_overview_meta_id"></xref> of the JPA Overview.
+described in <xref linkend="jpa_overview_meta_id"/> of the JPA Overview.
         </para>
         <para>
 To retrieve the identity value of a datastore identity entity, use the
 <methodname>OpenJPAEntityManager.getObjectId (Object entity)</methodname>
-method. See <xref linkend="ref_guide_runtime_em"></xref> for more information
on
+method. See <xref linkend="ref_guide_runtime_em"/> for more information on
 the <classname>OpenJPAEntityManager</classname>.
         </para>
         <example id="ref_guide_pc_oid_datastoreentityex">
@@ -520,7 +520,7 @@
             </para>
             <note>
                 <para>
-<xref linkend="ref_guide_integration_appidtool"></xref> describes the
+<xref linkend="ref_guide_integration_appidtool"/> describes the
 application identity tool's Ant task.
                 </para>
             </note>
@@ -535,8 +535,8 @@
             <para>
 The application identity tool accepts the standard set of command-line arguments
 defined by the configuration framework (see
-<xref linkend="ref_guide_conf_devtools"></xref> ), including code formatting
-flags described in <xref linkend="ref_guide_conf_devtools_format"></xref>. It
+<xref linkend="ref_guide_conf_devtools"/> ), including code formatting
+flags described in <xref linkend="ref_guide_conf_devtools_format"/>. It
 also accepts the following arguments:
             </para>
             <itemizedlist>
@@ -606,7 +606,7 @@
             </itemizedlist>
             <para>
 If you do not supply any arguments to the tool, it will act on the classes in
-your persistent classes list (see <xref linkend="ref_guide_pc_pcclasses"></xref>
+your persistent classes list (see <xref linkend="ref_guide_pc_pcclasses"/>
 ).
             </para>
         </section>
@@ -639,7 +639,7 @@
                 </secondary>
             </indexterm>
             <para>
-<xref linkend="jpa_overview_meta_gen"></xref> explains how to use JPA's
+<xref linkend="jpa_overview_meta_gen"/> explains how to use JPA's
 <literal>IDENTITY</literal> generation type to automatically assign field
 values. However, here are some additional caveats you should be aware of when
 using <literal>IDENTITY</literal> generation:
@@ -648,7 +648,7 @@
                 <listitem>
                     <para>
 Your database must support auto-increment / identity columns, or some equivalent
-(see <xref linkend="ref_guide_dbsetup_dbsupport_oracle"></xref> for how to
+(see <xref linkend="ref_guide_dbsetup_dbsupport_oracle"/> for how to
 configure a combination of triggers and sequences to fake auto-increment support
 in Oracle).
                     </para>
@@ -692,7 +692,7 @@
         </indexterm>
         <para>
 Bidirectional relations are an essential part of data modeling.
-<xref linkend="jpa_overview_mapping"></xref> in the JPA Overview explains how
to
+<xref linkend="jpa_overview_mapping"/> in the JPA Overview explains how to
 use the <literal>mappedBy</literal> annotation attribute to form bidirectional
 relations that also share datastore storage in JPA.
         </para>
@@ -1072,8 +1072,8 @@
                     </listitem>
                     <listitem>
                         <para>
-The field cannot have an externalizer (see <xref linkend="ref_guide_pc_extern">
-</xref> ).
+The field cannot have an externalizer (see <xref linkend="ref_guide_pc_extern"/>
+ ).
                         </para>
                     </listitem>
                     <listitem>
@@ -1229,10 +1229,10 @@
                     Externalizer Options
                 </title>
                 <tgroup cols="2" align="left" colsep="1" rowsep="1">
-                    <colspec colname="method">
-                    </colspec>
-                    <colspec colname="extension">
-                    </colspec>
+                    <colspec colname="method"/>
+                    
+                    <colspec colname="extension"/>
+                    
                     <thead>
                         <row>
                             <entry colname="method">
@@ -1335,10 +1335,10 @@
                     Factory Options
                 </title>
                 <tgroup cols="2" align="left" colsep="1" rowsep="1">
-                    <colspec colname="method">
-                    </colspec>
-                    <colspec colname="extension">
-                    </colspec>
+                    <colspec colname="method"/>
+                    
+                    <colspec colname="extension"/>
+                    
                     <thead>
                         <row>
                             <entry colname="method">
@@ -1451,7 +1451,7 @@
 field dirty manually in JPA.</phrase>
                 </para>
                 <para>
-See <xref linkend="ref_guide_pc_scos_proxy"></xref> for a discussion of proxies.
+See <xref linkend="ref_guide_pc_scos_proxy"/> for a discussion of proxies.
                 </para>
             </note>
             <para>
@@ -1462,7 +1462,7 @@
 complex as a collection or map of persistence-capable objects, or anything in
 between. If you do choose to externalize to a collection or map, OpenJPA
 recognizes a family of metadata extensions for specying type information for the
-externalized form of your fields - see <xref linkend="type"></xref>. If the
+externalized form of your fields - see <xref linkend="type"/>. If the
 external form of your field is a persistence-capable object, or contains
 persistence-capable objects, OpenJPA will correctly include the objects in its
 persistence-by-reachability algorithms and its delete-dependent algorithms.
@@ -1637,7 +1637,7 @@
 loading and eager fetching behavior.
         </para>
         <para>
-The JPA Overview's <xref linkend="jpa_overview_meta_fetch"></xref> describes
how
+The JPA Overview's <xref linkend="jpa_overview_meta_fetch"/> describes how
 to use JPA metadata annotations to control whether a field is fetched eagerly or
 lazily. Fetch groups add a dynamic aspect to this standard ability. As you will
 see, OpenJPA's JPA extensions allow you can add and remove fetch groups at
@@ -1831,7 +1831,7 @@
 public void clearFetchGroups ();
 </programlisting>
             <para>
-<xref linkend="ref_guide_runtime"></xref> details the <classname>
+<xref linkend="ref_guide_runtime"/> details the <classname>
 OpenJPAEntityManager</classname>, <classname>OpenJPAQuery</classname>,
and
 <classname>FetchPlan</classname> interfaces.
             </para>
@@ -2002,7 +2002,7 @@
         </para>
         <para>
 Eager fetching only affects relations in the fetch groups being loaded (see
-<xref linkend="ref_guide_fetch"></xref> ). In other words, relations that would
+<xref linkend="ref_guide_fetch"/> ). In other words, relations that would
 not normally be loaded immediately when retrieving an object or accessing a
 field are not affected by eager fetching. In our example above, the address of
 each person would only be eagerly fetched if the query were configured to
@@ -2042,7 +2042,7 @@
 Instead, OpenJPA defaults to <literal>parallel</literal> mode for collections,
 as described below. You can force OpenJPA use a join rather than parallel mode
 for a collection field using the metadata extension described in
-<xref linkend="eager-fetch-mode"></xref>.
+<xref linkend="eager-fetch-mode"/>.
                 </para>
                 <para>
                 <indexterm>
@@ -2072,8 +2072,8 @@
 Some databases may not support UNIONs or outer joins. Also, OpenJPA can not use
 outer joins if you have set the <link linkend="openjpa.jdbc.DBDictionary">
 <literal> DBDictionary</literal></link>'s <literal>JoinSyntax</literal>
to
-<literal>traditional</literal>. See <xref linkend="ref_guide_dbsetup_sql92">
-</xref>.
+<literal>traditional</literal>. See <xref linkend="ref_guide_dbsetup_sql92"/>
+.
                     </para>
                 </note>
             </listitem>
@@ -2116,7 +2116,7 @@
 Polymorphic to-one relations to table-per-class mappings use parallel eager
 fetching because proper joins are impossible. You can force other to-one
 relations to use parallel rather than join mode eager fetching using the
-metadata extension described in <xref linkend="eager-fetch-mode"></xref>.
+metadata extension described in <xref linkend="eager-fetch-mode"/>.
                 </para>
                 <para>
 Setting your subclass fetch mode to <literal>parallel</literal> affects
@@ -2196,7 +2196,7 @@
             <para>
 You can easily override the default fetch modes at runtime for any lookup or
 query through OpenJPA's fetch configuration APIs. See
-<xref linkend="ref_guide_runtime"></xref> for details.
+<xref linkend="ref_guide_runtime"/> for details.
             </para>
             <example id="ref_guide_perfpack_eager_def">
                 <title>
@@ -2227,14 +2227,14 @@
             </example>
             <para>
 You can specify a default subclass fetch mode for an individual class with the
-metadata extension described in <xref linkend="subclass-fetch-mode"></xref>.
+metadata extension described in <xref linkend="subclass-fetch-mode"/>.
 Note, however, that you cannot "upgrade" the runtime fetch mode with your class
 setting. If the runtime fetch mode is <literal>none</literal>, no eager
 subclass data fetching will take place, regardless of your metadata setting.
             </para>
             <para>
 This applies to the eager fetch mode metadata extension as well (see
-<xref linkend="eager-fetch-mode"></xref> ). You can use this extension to
+<xref linkend="eager-fetch-mode"/> ). You can use this extension to
 disable eager fetching on a field or to declare that a collection would rather
 use joins than parallel selects or vice versa. But an extension value of
 <literal>join</literal> won't cause any eager joining if the fetch
@@ -2269,7 +2269,7 @@
                         </secondary>
                     </indexterm>
 When you are using <literal>parallel</literal> eager fetch mode and you have
-large result sets enabled (see <xref linkend="ref_guide_dbsetup_lrs"></xref>)
+large result sets enabled (see <xref linkend="ref_guide_dbsetup_lrs"/>)
 or you place a range on a query, OpenJPA performs the needed parallel selects on
 one page of results at a time. For example, suppose your <literal>
 FetchBatchSize</literal> is set to 20, and you perform a large result set query
@@ -2316,7 +2316,7 @@
                     <para>
 OpenJPA cannot eagerly join to polymorphic relations to non-leaf classes in a
 table-per-class inheritance hierarchy. You can work around this restriction
-using the mapping extensions described in <xref linkend="nonpolymorphic"></xref>
+using the mapping extensions described in <xref linkend="nonpolymorphic"/>
 .
                     </para>
                 </listitem>
@@ -2374,7 +2374,7 @@
 <phrase> You specify a field's lock group in JPA metadata with the
 <ulink url="../apidocs/org/apache/openjpa/persistence/LockGroup.html">
 <classname>org.apache.openjpa.persistence.LockGroup</classname></ulink>
-annotation.</phrase> See <xref linkend="lock-group"></xref> for details
on lock
+annotation.</phrase> See <xref linkend="lock-group"/> for details on lock
 group metadata.
         </para>
         <example id="ref_guide_lock_groups_metadata">

Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_remote.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_remote.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_remote.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_remote.xml Tue Sep  5
12:28:36 2006
@@ -53,7 +53,7 @@
         </indexterm>
         <para>
 The JPA Overview describes the specification's standard detach and attach APIs
-in <xref linkend="jpa_overview_em_lifecycle"></xref>. This section enumerates

+in <xref linkend="jpa_overview_em_lifecycle"/>. This section enumerates 
 OpenJPA's enhancements to the standard behavior.
         </para>
         <section id="ref_guide_detach_behavior">
@@ -223,7 +223,7 @@
 <literal>fgs</literal>: Detach all fields and relations in the default fetch
 group, and any other fetch groups that you have added to the current
 <link linkend="ref_guide_runtime">fetch configuration</link>. For more
-information on custom fetch groups, see <xref linkend="ref_guide_fetch"></xref>
+information on custom fetch groups, see <xref linkend="ref_guide_fetch"/>
 .
                     </para>
                 </listitem>
@@ -241,14 +241,14 @@
             </para>
             <para>
 The <literal>openjpa.DetachState</literal> option is actually a plugin string
-(see <xref linkend="ref_guide_conf_plugins"></xref>) that allows you to also
+(see <xref linkend="ref_guide_conf_plugins"/>) that allows you to also
 configure the following options related to detached state:
             </para>
             <itemizedlist>
                 <listitem>
                     <para>
 <literal>DetachedStateField</literal>: As described in
-<xref linkend="ref_guide_attach_behavior"></xref> above, OpenJPA can take
+<xref linkend="ref_guide_attach_behavior"/> above, OpenJPA can take
 advantage of a <emphasis>detached state field</emphasis> to make the attach
 process more efficient. This field is added by the enhancer and is not visible
 to your application. Set this property to one of the following values:
@@ -279,7 +279,7 @@
                     <para>
 You can override the setting of this property or declare your own detached state
 field on individual classes using OpenJPA's metadata extensions. See
-<xref linkend="ref_guide_detach_field"></xref> below.
+<xref linkend="ref_guide_detach_field"/> below.
                     </para>
                 </listitem>
                 <listitem>
@@ -357,7 +357,7 @@
 field in your class metadata prevents the enhancer from adding any extra fields
 to the class, and keeps the enhanced class serialization-compatible with the
 unenhanced version. The detached state field must not be persistent. See
-<xref linkend="detached-state-field"></xref> for details on how to declare a
+<xref linkend="detached-state-field"/> for details on how to declare a
 detached state field.
                 </para>
 <programlisting>
@@ -423,7 +423,7 @@
         </indexterm>
 The remote event notification framework allows a subset of the information
 available through OpenJPA's transaction events (see
-<xref linkend="ref_guide_runtime_pm_event"></xref>) to be broadcast to remote
+<xref linkend="ref_guide_runtime_pm_event"/>) to be broadcast to remote
 listeners. OpenJPA's <link linkend="ref_guide_cache">data cache</link>, for
 example, uses remote events to remain synchronized when deployed in multiple
 JVMs.
@@ -586,7 +586,7 @@
 transactions is a function of the size of the connection pool. See the the
 <literal>MaxActive</literal> property of <literal>
 openjpa.ConnectionFactoryProperties</literal> in
-<xref linkend="ref_guide_dbsetup_builtin"></xref>. Setting a value of 0 will
+<xref linkend="ref_guide_dbsetup_builtin"/>. Setting a value of 0 will
 result in behavior where the thread invoking <methodname>commit</methodname>
 will perform the broadcast directly. Defaults to 2.
                         </para>

Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_runtime.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_runtime.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_runtime.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_runtime.xml Tue Sep 
5 12:28:36 2006
@@ -253,11 +253,11 @@
 details on the convenience methods it provides.
             </para>
         </section>
-        <section id="ref_guide_runtime_jpaquery">
+        <section id="ref_guide_runtime_jpaextent">
             <title>
                 Extent
             </title>
-            <indexterm zone="ref_guide_runtime_jpaquery">
+            <indexterm zone="ref_guide_runtime_jpaextent">
                 <primary>
                     Extent
                 </primary>
@@ -312,7 +312,7 @@
 can access this cache from your JPA code using the
 <ulink url="../../api/openjpa/persistence/StoreCache.html"><classname>
 org.apache.openjpa.persistence.StoreCache</classname></ulink> facade.
-<xref linkend="ref_guide_cache"></xref> has detailed information on OpenJPA's
+<xref linkend="ref_guide_cache"/> has detailed information on OpenJPA's
 data caching system, including the <classname>StoreCache</classname> facade.
             </para>
         </section>
@@ -330,7 +330,7 @@
 <ulink url="../../api/openjpa/persistence/QueryResultCache.html"><classname>
 org.apache.openjpa.persistence.QueryResultCache</classname></ulink> is an
 JPA-flavored facade to OpenJPA's internal query cache. See
-<xref linkend="ref_guide_cache_query"></xref> for details on query caching in
+<xref linkend="ref_guide_cache_query"/> for details on query caching in
 OpenJPA.
             </para>
         </section>
@@ -365,7 +365,7 @@
 org.apache.openjpa.persistence.jdbc.JDBCFetchPlan</classname></ulink> to add
 additional JDBC-specific tuning methods. Unless you have customized OpenJPA to
 use a non-relational back-end (see
-<xref linkend="ref_guide_enterprise_abstractstore"></xref> ), all <classname>
+<xref linkend="ref_guide_enterprise_abstractstore"/> ), all <classname>
 FetchPlan</classname>s in OpenJPA implement <classname>JDBCFetchPlan</classname>
 , so feel free to cast to this interface.
             </para>
@@ -383,7 +383,7 @@
 configuration does not affect the <classname> EntityManagerFactory</classname>.
             </para>
             <para>
-<xref linkend="ref_guide_fetch"></xref> includes examples using <classname>
+<xref linkend="ref_guide_fetch"/> includes examples using <classname>
 FetchPlan</classname> s.
             </para>
         </section>
@@ -1184,7 +1184,7 @@
 extensions by setting the <link linkend="openjpa.FilterListeners"><literal>
 openjpa.FilterListeners</literal></link> configuration property to a
 comma-separated list of plugin strings (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing your extensions
+<xref linkend="ref_guide_conf_plugins"/>) describing your extensions
 classes. Extensions registered in this fashion must have a public no-arg
 constructor. They must also be thread safe, because they will be shared across
 all queries.
@@ -1252,7 +1252,7 @@
 aggregates by setting the <link linkend="openjpa.AggregateListeners"><literal>
 openjpa.AggregateListeners</literal></link> configuration property to a
 comma-separated list of plugin strings (see
-<xref linkend="ref_guide_conf_plugins"></xref>) describing your aggregate
+<xref linkend="ref_guide_conf_plugins"/>) describing your aggregate
 implementation. Aggregates registered in this fashion must have a public no-arg
 constructor. They must also be thread safe, because they will be shared across
 all queries.
@@ -1384,7 +1384,7 @@
             </secondary>
         </indexterm>
         <para>
-The JPA Overview's <xref linkend="jpa_overview_mapping"></xref> details using
+The JPA Overview's <xref linkend="jpa_overview_mapping"/> details using
 generators to automatically populate identity fields in JPA.
         </para>
         <para>
@@ -1608,11 +1608,11 @@
 <classname>Seq</classname>s or your own <classname>Seq</classname>
 implementation. Set the <literal>sequenceName</literal> attribute to a plugin
 string describing your choice. See
-<xref linkend="jpa_overview_mapping_sequence"></xref> in the JPA Overview for
+<xref linkend="jpa_overview_mapping_sequence"/> in the JPA Overview for
 details on defining <literal>SequenceGenerator</literal> s.
         </para>
         <para>
-See <xref linkend="ref_guide_conf_plugins"></xref> for plugin string formatting.
+See <xref linkend="ref_guide_conf_plugins"/> for plugin string formatting.
         </para>
         <example id="ref_guide_sequence_named">
             <title>
@@ -1737,7 +1737,7 @@
 For details on the transaction framework, see the <literal>
 org.apache.openjpa.event</literal> package
 <ulink url="../apidocs/org/apache/openjpa/event/package.html">Javadoc</ulink>.
-Also see <xref linkend="ref_guide_event"></xref> for a description of OpenJPA's
+Also see <xref linkend="ref_guide_event"/> for a description of OpenJPA's
 remote event support.
         </para>
     </section>

Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml
URL: http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml?view=diff&rev=440450&r1=440449&r2=440450
==============================================================================
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml Tue Sep
 5 12:28:36 2006
@@ -11,14 +11,10 @@
             Supported Databases and JDBC Drivers
         </title>
         <tgroup rowsep="1" colsep="1" align="left" cols="4">
-            <colspec colname="dbname">
-            </colspec>
-            <colspec colname="dbversion">
-            </colspec>
-            <colspec colname="drivname">
-            </colspec>
-            <colspec colname="drivversion">
-            </colspec>
+            <colspec colname="dbname"/>
+            <colspec colname="dbversion"/>
+            <colspec colname="drivname"/>
+            <colspec colname="drivversion"/>
             <thead>
                 <row>
                     <entry colname="dbname">



Mime
View raw message