db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From arm...@apache.org
Subject cvs commit: db-ojb/forrest/src/documentation/content/xdocs site.xml
Date Wed, 28 Apr 2004 08:03:54 GMT
arminw      2004/04/28 01:03:54

  Modified:    forrest/src/documentation/content/xdocs/docu
                        advanced-technique.xml basic-technique.xml
                        deployment.xml howto-build-mappings.xml
                        howto-use-anonymous-keys.xml jdbc-types.xml
                        lockmanager.xml mapping-tutorial.xml
                        objectcache.xml performance.xml query.xml
                        repository.xml sequencemanager.xml
               forrest/src/documentation/content/xdocs site.xml
  Log:
  fix "anchor" element declaration
  
  Revision  Changes    Path
  1.5       +9 -11     db-ojb/forrest/src/documentation/content/xdocs/docu/advanced-technique.xml
  
  Index: advanced-technique.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/advanced-technique.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- advanced-technique.xml	27 Apr 2004 20:32:29 -0000	1.4
  +++ advanced-technique.xml	28 Apr 2004 08:03:52 -0000	1.5
  @@ -34,9 +34,9 @@
               </p>
           </section>
   
  +        <anchor id="polymorphism"/>
           <section>
               <title>Extents and Polymorphism</title>
  -            <anchor id="polymorphism"/>
               <p>
                   Working with inheritance hierarchies is a common task in object
                   oriented design and programming. Of course, any serious Java O/R tool
  @@ -687,9 +687,9 @@
               </section>
           </section>
   
  +        <anchor id="persistent-field"/>
           <section>
               <title>Change PersistentField Class</title>
  -            <anchor id="persistent-field"/>
               <p>
                   OJB supports a pluggable strategy to read and set the persistent
                   attributes in the persistence capable classes. All strategy implementation
  @@ -739,9 +739,9 @@
           </section>
   
   
  +        <anchor id="anonymous-keys"/>
           <section>
               <title>How do <em>anonymous keys</em> work?</title>
  -            <anchor id="anonymous-keys"/>
               <p>
                   To play for safety it is mandatory to understand how this feature is working.
In the HOWTO
                   section is detailed described <link href="site:howto/anonymous-keys">how
to use anoymous keys</link>.
  @@ -769,10 +769,9 @@
               </warning>
           </section>
   
  -
  +        <anchor id="using-rowreader"/>
           <section>
               <title>Using Rowreader</title>
  -            <anchor id="using-rowreader"/>
               <p>
                   RowReaders provide a Callback mechanism that allows to interact
                   with the OJB load mechanism. To understand how to use them we must
  @@ -900,9 +899,9 @@
                   materialization process and	provide additional features.
               </p>
   
  +            <anchor id="rowreader-example"/>
               <section>
                   <title>Rowreader Example</title>
  -                <anchor id="rowreader-example"/>
                   <p>
                       Assume that for some reason we do not want to map a 1:1 association
                       with a foreign key relationship to a different database table but
  @@ -967,9 +966,9 @@
           </section>
   
   
  +        <anchor id="nested-objects"/>
           <section>
               <title>Nested Objects</title>
  -            <anchor id="nested-objects"/>
               <p>
                   In the last section we discussed the usage of a user written RowReader
                   to implement nested objects. This approach has several disadvantages.
  @@ -1319,9 +1318,9 @@
           </section>
   
   
  +        <anchor id="manageable-collection"/>
           <section>
               <title>Manageable Collection</title>
  -            <anchor id="manageable-collection"/>
               <p>
                   In <link href="site:basic-technique/one-to-n">1:n</link> or
                   <link href="site:basic-technique/m-to-n">m:n</link> relations,
OJB can handle
  @@ -1535,10 +1534,9 @@
   
   
   
  -
  +        <anchor id="query-customizer"/>
           <section>
               <title>Customizing collection queries</title>
  -            <anchor id="query-customizer"/>
               <p>
                   Customizing the query used for collection retrieval allows a
                   <strong>developer</strong> to take
  
  
  
  1.3       +11 -11    db-ojb/forrest/src/documentation/content/xdocs/docu/basic-technique.xml
  
  Index: basic-technique.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/basic-technique.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- basic-technique.xml	27 Apr 2004 20:32:29 -0000	1.2
  +++ basic-technique.xml	28 Apr 2004 08:03:52 -0000	1.3
  @@ -28,9 +28,9 @@
       </header>
   
       <body>
  +        <anchor id="one-to-one"/>
           <section>
               <title>Mapping 1:1 associations</title>
  -            <anchor id="one-to-one"/>
               <p>
                   As a sample for a simple association we take the reference from an
                   article to its productgroup.
  @@ -297,9 +297,9 @@
           </section>
   
   
  +        <anchor id="one-to-n"/>
           <section>
               <title>Mapping 1:n associations</title>
  -            <anchor id="one-to-n"/>
               <p>
                   We will take a different perspective from the previous exmaple for
                   a 1:n association. We will associate multiple Articles with a
  @@ -532,9 +532,9 @@
           </section>
   
   
  +        <anchor id="m-to-n"/>
           <section>
               <title>Mapping m:n associations</title>
  -            <anchor id="m-to-n"/>
               <p>
                   OJB provides support for manually decomposed m:n associations as
                   well as an automated support for non decomposed m:n associations.
  @@ -953,9 +953,9 @@
           </section>
   
   
  +        <anchor id="cascading"/>
           <section>
               <title>Setting Load, Update, and Delete Cascading</title>
  -            <anchor id="cascading"/>
               <p>
                   As shown in the sections on 1:1, 1:n and m:n mappings, OJB manages
                   associations (or object references in Java terminology) by declaring
  @@ -1005,9 +1005,9 @@
                   The <em>auto-retrieve</em> setting is described below:
               </p>
   
  +            <anchor id="auto-retrieve"/>
               <section>
                   <title>auto-retrieve setting</title>
  -                <anchor id="auto-retrieve"/>
                   <p>
                       The
                       <code>auto-retrieve</code> attribute used in
  @@ -1083,9 +1083,9 @@
               </section>
   
   
  +            <anchor id="linking"/>
               <section>
                   <title>Link references</title>
  -                <anchor id="linking"/>
                   <p>If in
                       <code>reference-descriptor</code> or
                       <code>collection-descriptor</code> the
  @@ -1191,9 +1191,9 @@
           </section>
   
   
  +        <anchor id="using-proxy"/>
           <section>
               <title>Using Proxy Classes</title>
  -            <anchor id="using-proxy"/>
               <p>
                   Proxy classes can be used for &quot;lazy loading&quot; aka &quot;lazy
                   materialization&quot;. Using Proxy classes can help you in reducing
  @@ -1363,9 +1363,9 @@
                   <img src="images/proxies.gif" alt="proxy image"/>
               </p>
   
  +            <anchor id="dynamic-proxy"/>
               <section>
                   <title>Using Dynamic Proxies</title>
  -                <anchor id="dynamic-proxy"/>
                   <p>
                       The implementation of a proxy class is a boring task that repeats
                       the same delegation scheme for each new class. To liberate the
  @@ -1399,9 +1399,9 @@
                   </p>
               </section>
   
  +            <anchor id="single-proxy"/>
               <section>
                   <title>Using a Single Proxy for a Whole Collection</title>
  -                <anchor id="single-proxy"/>
                   <p>
                       A collection proxy represents a whole collection of objects, where
                       as a proxy class represents a single object.
  @@ -1455,9 +1455,9 @@
                   </p>
               </section>
   
  +            <anchor id="collection-proxy"/>
               <section>
                   <title>Customizing a Collection Proxy Class</title>
  -                <anchor id="collection-proxy"/>
                   <p>
                       The optional
                       <code>CollectionProxy</code> entry in
  
  
  
  1.3       +8 -7      db-ojb/forrest/src/documentation/content/xdocs/docu/deployment.xml
  
  Index: deployment.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/deployment.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- deployment.xml	24 Apr 2004 11:34:53 -0000	1.2
  +++ deployment.xml	28 Apr 2004 08:03:52 -0000	1.3
  @@ -92,9 +92,10 @@
                       lookup and must therefore be placed on the classpath.
                   </note>
               </section>
  +
  +            <anchor id="additional-jars"/>
               <section>
                   <title>3. Additional jar archives</title>
  -                <anchor id="additional-jars"/>
                   <p>
                       OJB depends on several other jar archives. These jar files are
                       shipped in the
  @@ -305,11 +306,11 @@
                   </p>
   
   
  +                <anchor id="jboss-ojb.properties"/>
                   <section>
                       <title>
                           <strong>1. Adapt OJB.properties file</strong>
                       </title>
  -                    <anchor id="jboss-ojb.properties"/>
                       <p>
                           If the PB-api is the only persistence API being used (no ODMG nor
JDO)
                           and it is
  @@ -561,11 +562,11 @@
                   </section>
   
   
  +                <anchor id="all-together"/>
                   <section>
                       <title>
                           <strong>7. Put all together</strong>
                       </title>
  -                    <anchor id="all-together"/>
                       <p>
                           Now put all files together. We keep the examples as simple as possible,
thus we deploy only
                           a ejb .jar file.
  @@ -642,9 +643,9 @@
               </section>
   
   
  +            <anchor id="example-beans"/>
               <section>
                   <title>Build example beans</title>
  -                <anchor id="example-beans"/>
                   <section>
                       <title>
                           <strong>Generate the sample session beans</strong>
  @@ -741,9 +742,9 @@
               </section>
   
   
  +            <anchor id="packing-ear"/>
               <section>
                   <title>Packing an .ear file</title>
  -                <anchor id="packing-ear"/>
                   <p>
                       Here is an example of the .ear package structure. It is redeployable
                       without having to restart JBoss.
  @@ -914,9 +915,9 @@
               </section>
   
   
  +            <anchor id="weblogic"/>
               <section>
                   <title>Instructions for Weblogic</title>
  -                <anchor id="weblogic"/>
                       <p>
                           <strong>1.</strong> Add the OJB jar files and depedencies
into the Weblogic classpath
                       </p>
  
  
  
  1.2       +2 -2      db-ojb/forrest/src/documentation/content/xdocs/docu/howto-build-mappings.xml
  
  Index: howto-build-mappings.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/howto-build-mappings.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- howto-build-mappings.xml	22 Apr 2004 19:29:50 -0000	1.1
  +++ howto-build-mappings.xml	28 Apr 2004 08:03:52 -0000	1.2
  @@ -249,8 +249,8 @@
   	</p>
   </section>
   
  +        <anchor id="xdoclet"/>
   <section><title>XDoclet transformation from Java code</title>
  -    <anchor id="xdoclet"/>
   	<p>
   		<link href="ext:xdoclet"><strong>XDoclet</strong></link><br/>
   		XDoclet is a code generation engine. It enables  Attribute-Oriented Programming  for
java.
  
  
  
  1.3       +2 -2      db-ojb/forrest/src/documentation/content/xdocs/docu/howto-use-anonymous-keys.xml
  
  Index: howto-use-anonymous-keys.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/howto-use-anonymous-keys.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- howto-use-anonymous-keys.xml	26 Apr 2004 18:25:20 -0000	1.2
  +++ howto-use-anonymous-keys.xml	28 Apr 2004 08:03:52 -0000	1.3
  @@ -113,9 +113,9 @@
           </section>
   
   
  +        <anchor id="how-it-works"/>
           <section>
               <title>How it works</title>
  -            <anchor id="how-it-works"/>
               <p>
                   To play for safety it is mandatory to understand how this feature is working.
More information
                   how it works <link href="site:advanced-technique/anonymous-keys">please
see here</link>.
  
  
  
  1.3       +3 -3      db-ojb/forrest/src/documentation/content/xdocs/docu/jdbc-types.xml
  
  Index: jdbc-types.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/jdbc-types.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- jdbc-types.xml	23 Apr 2004 19:17:46 -0000	1.2
  +++ jdbc-types.xml	28 Apr 2004 08:03:52 -0000	1.3
  @@ -28,9 +28,9 @@
   
       <body>
   
  +        <anchor id="jdbc-mapping"/>
           <section>
               <title>Mapping of JDBC Types to Java Types</title>
  -            <anchor id="jdbc-mapping"/>
               <p>
                   OJB implements the mapping conventions for JDBC and Java types as specified
by
                   the JDBC 3.0 specification.
  @@ -158,9 +158,9 @@
               </table>
           </section>
   
  +        <anchor id="field-conversion"/>
           <section>
               <title>Type and Value Conversions</title>
  -            <anchor id="field-conversion"/>
   
               <section>
                   <title>Introduction</title>
  
  
  
  1.2       +2 -2      db-ojb/forrest/src/documentation/content/xdocs/docu/lockmanager.xml
  
  Index: lockmanager.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/lockmanager.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- lockmanager.xml	23 Apr 2004 19:17:46 -0000	1.1
  +++ lockmanager.xml	28 Apr 2004 08:03:52 -0000	1.2
  @@ -1366,9 +1366,9 @@
           </section>
   
   
  +        <anchor id="distributed-locking"/>
           <section>
               <title>Locking in distributed environment</title>
  -            <anchor id="distributed-locking"/>
               <p>
                   ############ TODO ############
               </p>
  
  
  
  1.3       +3 -2      db-ojb/forrest/src/documentation/content/xdocs/docu/mapping-tutorial.xml
  
  Index: mapping-tutorial.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/mapping-tutorial.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- mapping-tutorial.xml	26 Apr 2004 18:25:20 -0000	1.2
  +++ mapping-tutorial.xml	28 Apr 2004 08:03:52 -0000	1.3
  @@ -97,8 +97,9 @@
                         metadata will specify what maps to what.
                     </p>
                 </section>
  +
  +            <anchor id="metadata"/>
                 <section><title>The Metadata</title>
  -                  <anchor id="metadata"/>
                     <p>
                         The <code>repository.xml</code> document is split into
several physical documents.
                         The <code>repository_user.xml</code> xml file is used
to contain user-defined
  
  
  
  1.4       +2 -3      db-ojb/forrest/src/documentation/content/xdocs/docu/objectcache.xml
  
  Index: objectcache.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/objectcache.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- objectcache.xml	27 Apr 2004 20:32:29 -0000	1.3
  +++ objectcache.xml	28 Apr 2004 08:03:52 -0000	1.4
  @@ -407,10 +407,9 @@
           </section>
   
   
  +        <anchor id="cache-filtering"/>
           <section>
               <title>CacheFilter feature</title>
  -
  -            <anchor id="cache-filtering"/>
               <p>
                   <strong>What does cache filtering mean</strong>
                   <br/>
  
  
  
  1.3       +6 -6      db-ojb/forrest/src/documentation/content/xdocs/docu/performance.xml
  
  Index: performance.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/performance.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- performance.xml	27 Apr 2004 20:32:29 -0000	1.2
  +++ performance.xml	28 Apr 2004 08:03:52 -0000	1.3
  @@ -65,9 +65,9 @@
               </p>
           </section>
   
  +        <anchor id="performance-test-suite"/>
           <section>
               <title>The Performance Test Suite</title>
  -            <anchor id="performance-test-suite"/>
               <p>
                   The
                   <em>OJB Performance Test Suite</em> allows to compare OJB
  @@ -138,9 +138,9 @@
           </section>
   
   
  +        <anchor id="compares-to-native"/>
           <section>
               <title>How OJB compares to native JDBC programming?</title>
  -            <anchor id="compares-to-native"/>
               <p>
                   OJB is shipped with tests compares native JDBC with ODMG and
                   PB-API implementation.
  @@ -276,9 +276,9 @@
           </section>
   
   
  +        <anchor id="multithreaded-performance"/>
           <section>
               <title>OJB performance in multi-threaded environments</title>
  -            <anchor id="multithreaded-performance"/>
               <p>
                   This test was created to check the performance and stability of the
                   supported API's (PB-api, ODMG-api, JDO-api) in a multithreaded environment.
  @@ -345,9 +345,9 @@
           </section>
   
   
  +        <anchor id="compares-to-other"/>
           <section>
               <title>How OJB compares to other O/R mapping tools?</title>
  -            <anchor id="compares-to-other"/>
               <p>
                   Many user ask this question and there is more than one answer. But OJB
was
                   shipped with a simple performance framework which allows a rudimentarily
  @@ -449,9 +449,9 @@
           </section>
   
   
  +        <anchor id="maximal-performance"/>
           <section>
               <title>What are the best settings for maximal performance?</title>
  -            <anchor id="maximal-performance"/>
               <p>
                   We don't know, that depends from the environment OJB runs (hardware, database,
driver, application server, ...).
                   But there are some settings which affect the performance:
  
  
  
  1.2       +6 -5      db-ojb/forrest/src/documentation/content/xdocs/docu/query.xml
  
  Index: query.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/query.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- query.xml	24 Apr 2004 11:30:34 -0000	1.1
  +++ query.xml	28 Apr 2004 08:03:52 -0000	1.2
  @@ -36,9 +36,10 @@
               </p>
           </section>
   
  +
  +        <anchor id="query-by-criteria"/>
           <section>
               <title>Query by Criteria</title>
  -            <anchor id="query-by-criteria"/>
               <p>
                   In this section you will learn how to use the query by criteria.
                   The classes are located in the package
  @@ -128,9 +129,9 @@
                           <li>and of course there negative forms</li>
                       </ul>
   
  +                <anchor id="in-not-in"/>
                   <section>
                       <title>in / not in</title>
  -                    <anchor id="in-not-in"/>
                       <p>
                           Some databases limit the number of parameters in an IN-statement.
                           <br/>
  @@ -572,9 +573,9 @@
               </section>
   
   
  +            <anchor id="querying-for-objects"/>
               <section>
                   <title>querying for objects</title>
  -                <anchor id="querying-for-objects"/>
                   <p>
                   OJB queries return
                   <strong>complete</strong> objects, that means all instance
variables are filled
  @@ -587,9 +588,9 @@
               </section>
   
   
  +            <anchor id="report-queries"/>
               <section>
                   <title>report queries</title>
  -                <anchor id="report-queries"/>
                   <p>
                   Report queries are used to retrieve row data, not 'real' business objects.
A row is an array of Object.
                   With these queries you can define what attributes of an object you want
to have in the row.
  
  
  
  1.3       +10 -13    db-ojb/forrest/src/documentation/content/xdocs/docu/repository.xml
  
  Index: repository.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/repository.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- repository.xml	27 Apr 2004 20:32:29 -0000	1.2
  +++ repository.xml	28 Apr 2004 08:03:52 -0000	1.3
  @@ -32,7 +32,7 @@
       <body>
   
           <section>
  -            <title>Introduction - repository syntax"</title>
  +            <title>Introduction - repository syntax</title>
               <p>
                   The syntax of the OJB repository xml files is defined by the
                   <em>repository.dtd</em>.
  @@ -85,12 +85,9 @@
           </section>
   
   
  -        <section>
  -            <title>Repository semantics</title>
  -            <p/>
  +            <anchor id="descriptor-repository"/>
               <section>
                   <title>descriptor-repository</title>
  -                <anchor id="descriptor-repository"/>
                   <p>
                       The
                       <em>descriptor-repository</em> is the root element of a
repository.xml file.
  @@ -194,9 +191,9 @@
               </section>
   
   
  +            <anchor id="jdbc-connection-descriptor"/>
               <section>
                   <title>jdbc-connection-descriptor</title>
  -                <anchor id="jdbc-connection-descriptor"/>
                   <p>
                       The
                       <em>jdbc-connection-descriptor</em> element specifies a
jdbc
  @@ -246,9 +243,9 @@
                           ]]></source>
                   </section>
   
  +                <anchor id="jcd-attributes"/>
                   <section>
                       <title>Attributes</title>
  -                    <anchor id="jcd-attributes"/>
                       <p>
                           The
                           <em>jdbc-connection-descriptor
  @@ -668,9 +665,9 @@
               </section>
   
   
  +            <anchor id="custom-attribute"/>
               <section>
                   <title>custom attribute</title>
  -                <anchor id="custom-attribute"/>
                   <p>
                       An
                       <em>attribute</em> element allows arbitrary name/value
pairs to
  @@ -693,9 +690,9 @@
               </section>
   
   
  +            <anchor id="class-descriptor"/>
               <section>
                   <title>class-descriptor</title>
  -                <anchor id="class-descriptor"/>
                   <p>
                       For interfaces or abstract classes a
                       <em>class-descriptor</em> holds a sequence
  @@ -835,9 +832,10 @@
   >]]></source>
               </section>
   
  +
  +            <anchor id="field-descriptor"/>
               <section>
                   <title>field-descriptor</title>
  -                <anchor id="field-descriptor"/>
                   <p>
                       A field descriptor contains mapping info for a primitive typed attribute
of a persistent class.
                       <br/>
  @@ -1095,9 +1093,9 @@
               </section>
   
   
  +            <anchor id="collection-descriptor"/>
               <section>
                   <title>collection-descriptor</title>
  -                <anchor id="collection-descriptor"/>
                   <p>
                       A collection-descriptor contains mapping info for a Collection- or
                       Array-attribute of a  persistent class that contains persistent
  @@ -1544,7 +1542,6 @@
   >]]></source>
                   </section>
               </section>
  -        </section>
       </body>
   </document>
   
  
  
  
  1.3       +14 -14    db-ojb/forrest/src/documentation/content/xdocs/docu/sequencemanager.xml
  
  Index: sequencemanager.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/sequencemanager.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- sequencemanager.xml	26 Apr 2004 23:34:43 -0000	1.2
  +++ sequencemanager.xml	28 Apr 2004 08:03:52 -0000	1.3
  @@ -183,9 +183,9 @@
                       sequence manager implementation.
                   </p>
   
  +                <anchor id="high-low"/>
                   <section>
                       <title>High/Low sequence manager</title>
  -                    <anchor id="high-low"/>
                       <p>
                           Per default OJB internally uses a High/Low algorithm based sequence
manager
                           for the generation of unique ids, as described in
  @@ -268,9 +268,9 @@
                   </section>
   
   
  +                <anchor id="in-memory"/>
                   <section>
                       <title>In-Memory sequence manager</title>
  -                    <anchor id="in-memory"/>
                       <p>
                           Another sequence manager implementation is a
                           <em>In-Memory</em> version
  @@ -312,9 +312,9 @@
                   </section>
   
   
  +                <anchor id="database-sequences-based"/>
                   <section>
                       <title>Database sequences based implementation</title>
  -                    <anchor id="database-sequences-based"/>
                       <p>
                           If your database support sequence key generation (e.g. Oracle,
SAP DB, PostgreSQL)
                           you could use the
  @@ -382,9 +382,9 @@
                   </section>
   
   
  +                <anchor id="high-low-sequences"/>
                   <section>
                       <title>Database sequences based high/low implementation</title>
  -                    <anchor id="high-low-sequences"/>
                       <p>
                           Based on the sequence manager implementation described above, but
                           use a high/low algorithm to avoid database access.
  @@ -505,9 +505,9 @@
                   </section>
   
   
  +                <anchor id="mssql-guid"/>
                   <section>
                       <title>Microsoft SQL Server 'uniqueidentifier' type (GUID) sequencing</title>
  -                    <anchor id="mssql-guid"/>
                       <p>
                           For those users you are using SQL Server 7.0 and up, the uniqueidentifier
                           was introduced, and allows for your rows Primary Keys to be GUID's
that are
  @@ -562,9 +562,9 @@
                   </section>
   
   
  +                <anchor id="native"/>
                   <section>
                       <title>Identity based sequence manager</title>
  -                    <anchor id="native"/>
                       <p>
                           This sequence manager implementation supports database Identity
columns
                           (supported by MySQL, MsSQL, HSQL, ...). When using identity columns
we have to do
  @@ -625,9 +625,9 @@
               </section>
   
   
  +            <anchor id="how-to-write"/>
               <section>
                   <title>How to write my own sequence manager?</title>
  -                <anchor id="how-to-write"/>
                   <p>
                       Very easy to do, just write a implementation class of the
                       interface
  @@ -681,9 +681,9 @@
               <section>
                   <title>Questions</title>
   
  +                <anchor id="when-using"/>
                   <section>
                       <title>When using sequence-name attribute in field-descriptor?</title>
  -                    <anchor id="when-using"/>
                       <p>
                           Most
                           <code>SequenceManager</code> implementations based
on sequence names.
  @@ -738,9 +738,9 @@
                   </section>
   
   
  +                <anchor id="no-auto-build"/>
                   <section>
                       <title>How could I prevent auto-build of the sequence-name?</title>
  -                    <anchor id="no-auto-build"/>
                       <p>
                           All shipped
                           <code>SequenceManager</code> implementations which
using sequence names
  @@ -763,9 +763,9 @@
   </sequence-manager>]]></source>
                   </section>
   
  +                <anchor id="sequenceManagerHandling"/>
                   <section>
                       <title>Sequence manager handling using multiple databases</title>
  -                    <anchor id="sequenceManagerHandling"/>
                       <p>
                           If you use multiple databases you have to declare a sequence manager
in each
                           <code>jdbc-connection-descriptor</code>. If you don't
specify a sequence manager
  @@ -774,9 +774,9 @@
                       </p>
                   </section>
   
  +                <anchor id="oneSequenceManager"/>
                   <section>
                       <title>One sequence manager with multiple databases?</title>
  -                    <anchor id="oneSequenceManager"/>
                       <p>
                           OJB was intended to use a sequence manager per database. But it
                           shouldn't be complicated to realize a global sequence manager
  @@ -786,9 +786,9 @@
                   </section>
   
   
  +                <anchor id="directAccess"/>
                   <section>
                       <title>Can I get direct access to the sequence manager?</title>
  -                    <anchor id="directAccess"/>
                       <p>
                           That's no problem:
                       </p>
  @@ -812,9 +812,9 @@
                   </section>
   
   
  +                <anchor id="pitfalls"/>
                   <section>
                       <title>Any known pitfalls?</title>
  -                    <anchor id="pitfalls"/>
                       <ul>
                           <li>
                               When enable a sequence manager implementation based on
  
  
  
  1.7       +12 -8     db-ojb/forrest/src/documentation/content/xdocs/site.xml
  
  Index: site.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/site.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- site.xml	27 Apr 2004 20:32:30 -0000	1.6
  +++ site.xml	28 Apr 2004 08:03:54 -0000	1.7
  @@ -30,7 +30,6 @@
   -->
   <!-- @version $Id$ -->
   <site label="OJB" href="" xmlns="http://apache.org/forrest/linkmap/1.0" tab="home">
  -
       <ojb label="OJB">
           <index label="Home" href="index.html" description="OJB index page"/>
           <features label="Features" href="features.html" description="OJB features"/>
  @@ -47,10 +46,6 @@
               <more-or href="#more-or"/>
           </links>
           <!-- dependencies label="Dependencies" href="dependencies.html"/ -->
  -        <all label="All">
  -            <whole_site_html label="Whole Site HTML" href="site.html"/>
  -            <whole_site_html label="Whole Site PDF" href="site.pdf"/>
  -        </all>
       </ojb>
   
       <download label="Download">
  @@ -159,11 +154,20 @@
       </documentation>
   
   
  +    <!-- all label="Whole site">
  +        <all_site label="Full HTML" href="site.html"/>
  +        <all_sitePDF label="Full PDF" href="site.pdf"/>
  +    </all-->
  +
  +    <!-- all tab="home" label="All">
  +        <whole_site_html tab="home" label="Whole site HTML" href="site.html"/>
  +        <whole_site_pdf tab="home" label="Whole site PDF" href="site.pdf"/>
  +    </all -->
   
       <!-- Usage example: <link href="ext:jakarta/tomcat">XXX</link> -->
       <external-refs>
           <!-- TODO fix this link -->
  -        <javadoc href="">
  +        <javadoc href="api/">
               <metadata-manager href="org/apache/ojb/broker/metadata/MetadataManager.html"/>
           </javadoc>
           <ojb>
  @@ -237,7 +241,7 @@
           <tangosol-blog href="http://www.freeroller.net/page/jmckerr"/>
           <javagroups href="http://www.jgroups.org/javagroupsnew/docs/index.html"/>
           <ambysoft href="http://www.ambysoft.com/mappingObjects.html"/>
  -        <axgen href=""/>
  +        <axgen href="http://axgen.sourceforge.net/"/>
           <sun href="http://java.sun.com/">
               <jdo href="products/jdo/">
                   <javadoc href="javadocs/index.html"/>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message