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 features.xml site.xml
Date Wed, 12 May 2004 16:06:12 GMT
arminw      2004/05/12 09:06:11

  Modified:    forrest/src/documentation/content/xdocs/docu deployment.xml
                        faq.xml metadata.xml objectcache.xml
               forrest/src/documentation/content/xdocs features.xml
                        site.xml
  Log:
  add more documentation
  
  Revision  Changes    Path
  1.5       +2 -1      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.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- deployment.xml	3 May 2004 23:14:45 -0000	1.4
  +++ deployment.xml	12 May 2004 16:06:11 -0000	1.5
  @@ -260,6 +260,7 @@
           </section>
   
   
  +        <anchor id="j2ee-server"/>
           <section>
               <title>Deployment in EJB based applications</title>
   
  
  
  
  1.7       +23 -2     db-ojb/forrest/src/documentation/content/xdocs/docu/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/faq.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- faq.xml	12 May 2004 00:47:35 -0000	1.6
  +++ faq.xml	12 May 2004 16:06:11 -0000	1.7
  @@ -1076,8 +1076,29 @@
                       Define for each database a
                       <code>jdbc-connection-descriptor</code>, use the
                       different
  -                    <code>jcdAlias</code> names to match the according database.
  +                    <code>jcdAlias</code> names in the <link href="site:repository">repositry
file</link>
  +                    to match the according database.
                   </p>
  +                <source><![CDATA[
  +<jdbc-connection-descriptor
  +    jcd-alias="myFirstDb"
  +    ...
  +>
  +    ...
  +</jdbc-connection-descriptor>
  +
  +<jdbc-connection-descriptor
  +    jcd-alias="mySecondDb"
  +    ...
  +>
  +    ...
  +</jdbc-connection-descriptor>]]></source>
  +                
  +                <note>
  +                    OJB does not provide distributed transactions by itself. To use distributed
transactions,
  +                    OJB have to be <link href="site:deployment/j2ee-server">integrated
in an j2ee conform environment</link>
  +                    (or made work with an JTA/JTS implementation).
  +                </note>
               </answer>
           </faq>
   
  
  
  
  1.3       +189 -56   db-ojb/forrest/src/documentation/content/xdocs/docu/metadata.xml
  
  Index: metadata.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/metadata.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- metadata.xml	12 May 2004 00:47:35 -0000	1.2
  +++ metadata.xml	12 May 2004 16:06:11 -0000	1.3
  @@ -92,7 +92,8 @@
                   to start OJB
                   <link href="#without-repository">with an empty repository file</link>
or only
                   <link href="#load-connection-metadata">load connection metadata</link>
  -                and <link href="#metadata-at-runtime">object metadata at runtime</link>
or what ever
  +                and
  +                <link href="#metadata-at-runtime">object metadata at runtime</link>
or what ever
                   combination fit your requirements.
               </p>
           </section>
  @@ -113,8 +114,11 @@
                   must be declared. This element encapusaltes the connection specific metadata
information.
               </p>
               <p>
  -                The <em>JdbcConnectionDescriptor</em> instances are managed
by
  -                <link href="ext:api/connection-repository"><code>org.apache.ojb.broker.metadata.ConnectionRepository</code></link>
  +                The
  +                <em>JdbcConnectionDescriptor</em> instances are managed by
  +                <link href="ext:api/connection-repository">
  +                    <code>org.apache.ojb.broker.metadata.ConnectionRepository</code>
  +                </link>
               </p>
   
   
  @@ -173,9 +177,13 @@
       </jdbc-connection-descriptor>
   </descriptor-repository>]]></source>
                   <p>
  -                    In the above additional repository file two new <em>jdbc-connection-descriptor</em>
  -                    (new databases) <em>runtime</em> and <em>minimal</em>
are declared, to load and merge
  -                    the additional connection metadata the <em>MetadataManager was
used:</em>
  +                    In the above additional repository file two new
  +                    <em>jdbc-connection-descriptor</em>
  +                    (new databases)
  +                    <em>runtime</em> and
  +                    <em>minimal</em> are declared, to load and merge
  +                    the additional connection metadata the
  +                    <em>MetadataManager was used:</em>
                   </p>
                   <source><![CDATA[
   // get MetadataManager instance
  @@ -198,15 +206,19 @@
               <p>
                   The
                   <em>object metadata</em> encapsulate all information referring
to the persistent capable
  -                java objects and the associated tables in database. <em>Object metadata</em>
must be declared in
  +                java objects and the associated tables in database.
  +                <em>Object metadata</em> must be declared in
                   <link href="site:repository">OJB repository file</link>.
                   <br/>
                   Each persistence capable java object must be declared in a corresponding
                   <link href="site:repository/class-descriptor">class-descriptor</link>.
               </p>
               <p>
  -                The <em>ClassDescriptor</em> instances are managed by
  -                <link href="ext:api/descriptor-repository"><code>org.apache.ojb.broker.metadata.DescriptorRepository</code></link>.
  +                The
  +                <em>ClassDescriptor</em> instances are managed by
  +                <link href="ext:api/descriptor-repository">
  +                    <code>org.apache.ojb.broker.metadata.DescriptorRepository</code>
  +                </link>.
                   Per default OJB use only one global instance of this class.
               </p>
   
  @@ -246,11 +258,14 @@
           />
       </class-descriptor>
   </descriptor-repository>]]></source>
  -            <p>
  -                To load and merge the object metadata of the additional repository files
first read
  -                the metadata using the <link href="ext:api/metadata-manager"><em>MetadataManager</em></link>.
  -            </p>
  -            <source><![CDATA[
  +                <p>
  +                    To load and merge the object metadata of the additional repository
files first read
  +                    the metadata using the
  +                    <link href="ext:api/metadata-manager">
  +                        <em>MetadataManager</em>
  +                    </link>.
  +                </p>
  +                <source><![CDATA[
   // get MetadataManager instance
   MetadataManager mm = MetadataManager.getInstance();
   
  @@ -259,50 +274,160 @@
   
   // merge the new class-descriptor with existing object metadata
   mm.mergeDescriptorRepository(dr);]]></source>
  -            <p>
  -                It is also possible to keep the different <em>object metadata</em>
for the same classes
  -                parallel by using <link href="#metadata-profiles"><em>metadata
profiles</em></link>.
  -            </p>
  -                </section>
  +                <p>
  +                    It is also possible to keep the different
  +                    <em>object metadata</em> for the same classes
  +                    parallel by using
  +                    <link href="#metadata-profiles">
  +                        <em>metadata profiles</em>
  +                    </link>.
  +                </p>
  +            </section>
   
   
  +            <anchor id="global-changes"/>
               <section>
  -            <title>Global <em>object metadata</em> changes</title>
  -            <p>
  -                Per default OJB use a global instance of class
  -                <link href="ext:api/descriptor-repository"><em>DescriptorRepository</em></link>
to manage all
  -                <em>object metadata</em>. This means that all <em>PersistenceBroker</em>
instances (kernel component
  -                used by all top-level api) use the same object metadata.
  -            </p>
  -            <p>
  -                So changes of the object metadata (e.g. remove of a collection-descriptor)
will be seen
  -                immediately by all <em>PersistenceBroker</em> instances.
  -                XXXXXXXXXXXXXXXXXXX TODO XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  -            </p>
  -            <p>
  -                The <link href="ext:api/metadata-manager"><em>MetadataManager</em></link>
  -                provide several methods to read/set and manipulate object metadata.
  -            </p>
  -        </section>
  -        </section>
  +                <title>Global
  +                    <em>object metadata</em> changes
  +                </title>
  +                <p>
  +                    The
  +                    <link href="ext:api/metadata-manager">
  +                        <em>MetadataManager</em>
  +                    </link>
  +                    provide several methods to read/set and manipulate object metadata.
  +                </p>
  +                <p>
  +                    Per default OJB use a global instance of class
  +                    <link href="ext:api/descriptor-repository">
  +                        <em>DescriptorRepository</em>
  +                    </link> to manage all
  +                    <em>object metadata</em>. This means that all
  +                    <em>PersistenceBroker</em> instances (kernel component
  +                    used by all top-level api) use the same object metadata.
  +                </p>
  +                <p>
  +                    So changes of the object metadata (e.g. remove of a CollectionDescriptor
instance from a
  +                    ClassDescriptor) will be seen immediately by all
  +                    <em>PersistenceBroker</em> instances.
  +                    This is in most cases not the favoured behaviour and OJB supports
  +                    <link href="#per-thread-changes">per thread changes of object
metadata</link>.
  +                </p>
   
  +            </section>
   
  +            <anchor id="per-thread-changes"/>
  +            <section>
  +                <title>Per thread metadata changes</title>
  +                <p>
  +                    Per default the manager handle one global
  +                    <link href="ext:api/descriptor-repository">
  +                        <em>DescriptorRepository</em>
  +                    </link> for all calling threads
  +                    (keep in mind PB-api is not threadsafe, thus each thread use it's own
PersistenceBroker instance),
  +                    but it is ditto possible to use different
  +                    <em>metadata profiles</em> in a per thread manner -
  +                    profiles means different instances of DescriptorRepository  objects.
Each thread/PersistenceBroker instance
  +                    can be associated with a specific
  +                    <em>DescriptorRepository</em> instance. All made object
metadata
  +                    changes only will be seen by the PersistenceBroker instances using
the same DescriptorRepository instance.
  +                    In theory each PersistenceBroker instance could be associated with
a separate instance of object
  +                    metadata, but the recommended way is to use
  +                    <link href="#metadata-profiles">metadata profiles</link>.
  +                </p>
  +                <p>
  +                    To enable the use of different
  +                    <em>DescriptorRepository</em> instances for each thread
do:
  +                </p>
  +                <anchor id="per-thread-mode"/>
  +                <source><![CDATA[
  +MetadataManager mm = MetadataManager.getInstance();
  +// tell the manager to use per thread mode
  +mm.setEnablePerThreadChanges(true);
  +...]]></source>
  +                <p>
  +                    This can be done e.g. at start up or at runtime when it's needed.
  +                    Now it's possible to use dedicated DescriptorRepository instances per
thread:
  +                </p>
  +                <source><![CDATA[
  +// e.g get a coppy of the global repository
  +DescriptorRepository dr = mm.copyOfGlobalRepository();
  +// now we can manipulate the persistent object metadata of the copy
  +......
  +
  +// set the changed repository for current thread
  +mm.setDescriptor(dr);
  +
  +// now let this thread lookup a PersistenceBroker instance
  +// with the modified metadata
  +// all other threads use still the global object metadata
  +PersistenceBroker broker = PersistenceBrokerFactory.createPersistenceBroker(myKey)]]></source>
  +            </section>
  +            <note>
  +                Set object metadata (setting of the DescriptorRepository) before lookup
the PersistenceBroker instance
  +                for current thread, because the metadata was bound to the PersistenceBroker
instance at lookup.
  +            </note>
   
  -        <anchor id="metadata-profiles"/>
  -        <section>
  -            <title>Object metadata profiles</title>
  -            <p>
  -                XXXXXXXXXXXXX TODO XXXXXXXXXXXXXX
  -            </p>
  -        </section>
   
  +            <anchor id="metadata-profiles"/>
  +            <section>
  +                <title>Object metadata profiles</title>
  +                <p>
  +                    MetadataManager was shipped with a simple mechanism to add, remove
and load different
  +                    <em>persistent objects metadata profiles</em> (different
DescriptorRepository instances)
  +                    in a per thread manner. Use method
  +                    <em>addProfile</em> to add different persistent object
  +                    metadata profiles, method
  +                    <em>removeProfile</em> to remove profiles and
  +                    <em>loadProfile</em> load a profile for the calling thread.
  +                </p>
  +                <source><![CDATA[
  +// get MetadataManager instance
  +MetadataManager mm = MetadataManager.getInstance();
   
  -        <section>
  -            <title>Reference runtime changes on per query basis</title>
  -            <fixme author="arminw">
  -                Changes of reference settings on a per query basis will be supported with
  -                next upcoming release 1.1
  -            </fixme>
  +// enable per thread mode if not done before
  +mm.setEnablePerThreadChanges(true);
  +
  +// Load additional object metadata by parsing an repository file
  +DescriptorRepository dr_1 = mm.readDescriptorRepository("pathOrURLtoFile_1");
  +DescriptorRepository dr_2 = mm.readDescriptorRepository("pathOrURLtoFile_2");
  +
  +// add  profiles
  +mm.addProfile("global", mm.copyOfGlobalRepository());
  +mm.addProfile("guest", dr_1);
  +mm.addProfile("admin", dr_2);
  +
  +// now load a specific profile
  +mm.loadProfile("admin");
  +broker = PersistenceBrokerFactory.defaultPersistenceBroker();]]></source>
  +                <p>
  +                    After the
  +                    <em>loadProfile</em> call all PersistenceBroker instances
will be associated
  +                    with the
  +                    <em>admin</em> profile.
  +                </p>
  +                <note>
  +                    Method
  +                    <em>loadProfile</em> only proper work if the
  +                    <link href="#per-thread-mode">per thread mode</link> is
enabled.
  +                </note>
  +            </section>
  +
  +
  +            <section>
  +                <title>Reference runtime changes on per query basis</title>
  +                <fixme author="arminw">
  +                    Changes of reference settings on a per query basis will be supported
with
  +                    next upcoming release 1.1
  +                </fixme>
  +            </section>
  +
  +            <section>
  +                <title>Pitfalls</title>
  +                <p>
  +                    
  +                </p>
  +            </section>
           </section>
   
   
  @@ -343,14 +468,19 @@
                   </p>
                   <ul>
                       <li>load connection metadata by parsing additional repository
files</li>
  -                    <li>create the <em>JdbcConnectionDescriptor</em>
at runtime</li>
  +                    <li>create the
  +                        <em>JdbcConnectionDescriptor</em> at runtime
  +                    </li>
                   </ul>
                   <p>
                       The first one is described in section
                       <link href="#load-connection-metadata">load and merge connection
metadata</link>.
                       For the second one a new instance of class
  -                    <link href="ext:api/jdbc-connection-descriptor"><code>org.apache.ojb.broker.metadata.JdbcConnectionDescriptor</code></link>
  -                    is needed. The prepared instance will be passed to class <em>ConnectionRepository</em>:
  +                    <link href="ext:api/jdbc-connection-descriptor">
  +                        <code>org.apache.ojb.broker.metadata.JdbcConnectionDescriptor</code>
  +                    </link>
  +                    is needed. The prepared instance will be passed to class
  +                    <em>ConnectionRepository</em>:
                   </p>
                   <source><![CDATA[
   ConnectionRepository cr = MetadataManager.getInstance().connectionRepository();
  @@ -383,7 +513,8 @@
                       <code>class-descriptor</code>) at runtime?
                   </title>
                   <p>
  -                    There are two possibilities to add new <em>object metadata</em>
at runtime:
  +                    There are two possibilities to add new
  +                    <em>object metadata</em> at runtime:
                   </p>
                   <ul>
                       <li>load object metadata by parsing additional repository files</li>
  @@ -395,7 +526,9 @@
                   </p>
                   <p>
                       To create and add new metadata objects at runtime we create new
  -                    <link href="ext:api/class-descriptor"><code>org.apache.ojb.broker.metadata.ClassDescriptor</code></link>
  +                    <link href="ext:api/class-descriptor">
  +                        <code>org.apache.ojb.broker.metadata.ClassDescriptor</code>
  +                    </link>
                       instances at runtime and using the
                       <code>MetadataManager</code> to add them to OJB:
                   </p>
  
  
  
  1.5       +2 -1      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.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- objectcache.xml	28 Apr 2004 08:03:52 -0000	1.4
  +++ objectcache.xml	12 May 2004 16:06:11 -0000	1.5
  @@ -372,6 +372,7 @@
           </section>
   
   
  +        <anchor id="distributed-cache"/>
           <section>
               <title>Distributed ObjectCache?</title>
               <p>
  
  
  
  1.4       +35 -49    db-ojb/forrest/src/documentation/content/xdocs/features.xml
  
  Index: features.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/features.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- features.xml	27 Apr 2004 20:32:30 -0000	1.3
  +++ features.xml	12 May 2004 16:06:11 -0000	1.4
  @@ -31,25 +31,36 @@
               <title>Features</title>
               <ul>
                   <li>
  -                    The PersistenceBroker allows Java Programmers to store and retrieve
Java
  -                    Objects in/from JDBC-compliant RDBMS
  +                    Support of standard and prorietary API's:
  +                    <ul>
  +                        <li>PB api (prorietary)</li>
  +                        <li>OTM api (prorietary)</li>
  +                        <li>ODMG api (standard)</li>
  +                        <li>JDO api (standard)</li>
  +                    </ul>
                   </li>
                   <li>
  -                    Transparent persistence: Persistent classes don't have to inherit from
a
  -                    persistent base class or to implement an interface.
  +                    The PersistenceBroker kernel api and all top-level api (ODMG, OTM,
JDO) allows Java
  +                    Programmers to store and retrieve Java Objects in/from (any) JDBC-compliant
RDBMS
                   </li>
                   <li>
  -                    Persistence by reachability: All Objects associated to a persistent
object
  -                    by references are made persitent too.
  +                    Transparent persistence: Persistent classes don't have to inherit from
a
  +                    persistent base class or to implement an interface.
                   </li>
                   <li>
                       Scalable architecture that allows to build
                       massively distributed and clustered systems.
                   </li>
                   <li>
  -                    Extremly flexible design with pluggable implementation of most service
classes
  -                    like PersistenceBroker, ObjectCache, SequenceManager, RowReader, ConnectionFactory,
  -                    ConnectionManager, IndirectionHandler, SQLGenerator, JdbcAccess and
so on.
  +                    <link href="site:basic-technique">Configurable persistence by
reachability</link>:
  +                    All Objects associated to a persistent object by references can made
persitent too.
  +                </li>
  +                <li>
  +                    Extremly flexible design with pluggable implementation of most
  +                    service classes like <em>PersistenceBroker</em>, <em>ObjectCache</em>,
  +                    <em>SequenceManager</em>, <em>RowReader</em>,
<em>ConnectionFactory</em>,
  +                    <em>ConnectionManager</em>, <em>IndirectionHandler</em>,
<em>SQLGenerator</em>,
  +                    <em>JdbcAccess</em>, ... and so on.
                   </li>
                   <li>
                       Quality assurance taken seriously: More than
  @@ -66,7 +77,8 @@
                   </li>
                   <li>
                       <link href="site:basic-technique/cascading">Automatic</link>
and
  -                    <link href="site:basic-technique/linking">manual</link>
assignment of foreign key values.
  +                    <link href="site:basic-technique/linking">manual</link>
  +                    assignment of foreign key values.
                   </li>
                   <li>
                       The Object / Relational mapping is defined in an XML Repository. The
  @@ -75,7 +87,7 @@
                       for maximum flexibility
                   </li>
                   <li>
  -                    Classes can be mapped to an arbitrary number of JDBC datasources.
  +                    Easy use of <link href="site:faq/multiple-databases">multiple
databases</link>.
                   </li>
                   <li>
                       Configurable Lazy Materialization through
  @@ -86,8 +98,7 @@
                   </li>
                   <li>
                       Support for
  -                    <link href="site:advanced-technique/polymorphism">Polymorphism
  -                    </link> and ODMG Extents.
  +                    <link href="site:advanced-technique/polymorphism">Polymorphism
and Extents</link>.
                       You can use Interface-types and
                       abstract classes as attribute types in your persistent classes. Queries
                       are also aware of extents: A query against a baseclass or interface
will
  @@ -114,8 +125,8 @@
                       Reusing Prepared Statements, internal <link href="site:connection">connection
pooling</link>.
                   </li>
                   <li>
  -                    Integrates smoothly in controlled environments like EJB containers
  -                    (wrt. SecurityManagers and JNDI based Datasources).
  +                    Integrates smoothly in controlled environments like
  +                    <link href="site:deployment/j2ee-server">EJB containers</link>
                   </li>
                   <li>
                       Full JTA and JCA (in progress) Integration.
  @@ -126,52 +137,27 @@
                       to minimize the number of queries.
                   </li>
                   <li>
  -                    ODMG compliant API, a Tutorial, and TestCases are included.
  +                    ODMG compliant API, <link href="site:odmg-tutorial">a Tutorial</link>,
and TestCases are included.
                   </li>
                   <li>
  -                    JDO 1.0.1 compliant API (based on jdori, native implemetnation in progress),
  -                    a Tutorial, and TestCases are included.
  +                    JDO 1.0.1 compliant API (based on jdori, native implementation in progress),
  +                    <link href="site:jdo-tutorial">a Tutorial</link>, and TestCases
are included.
                   </li>
                   <li>
                       Distributed
  -                    <link href="site:lock-manager">Lockmanagement
  -                    </link> supporting four pessimistic
  +                    <link href="site:lock-manager">Lockmanagement</link>
  +                    supporting four pessimistic
                       Transaction Isolation Levels (uncommited or &quot;dirty&quot;
reads,
                       commited reads, repeatable reads, serializable transactions).
                   </li>
                   <li>
  -                    <link href="site:faq/">
  -                    </link>Optimistic locking support. Users may declare
  +                    <link href="site:faq/optimistic-locking">Optimistic locking</link>
support.
  +                    Users may declare
                       <code>int</code> or <code>long</code> fields
as version attributes or
                       <code>java.sql.Timestamp</code> fields as timestamp attributes.
                   </li>
                   <li>
  -                    Cache synchronisation for distributed <link href="site:object-cache">caches</link>.
  -                </li>
  -                <li>
  -                    The Broker uses an internal <link href="site:object-cache">ObjectCache</link>
which
  -                    <ul>
  -                        <li>
  -                            maintains object identity (multiple lookups on a given table
with same
  -                            primary key will return one and the same object !)
  -                        </li>
  -                        <li>reduces read and write overhead against databases</li>
  -                        <li>prevents circular reads in object read phase</li>
  -                        <li>
  -                            is fully garbage collectable through usage of soft references
(if
  -                            objects are referenced by the ObjectCache but not from any
  -                            Client-Application they can be reclaimed by the garbage collector)
  -                        </li>
  -                        <li>
  -                            The CacheMechanism is pluggable and can be easily replaced
with
  -                            user-defined implementations. There are also some predefined
  -                            implementations available.
  -                        </li>
  -                        <li>
  -                            Provides a cache synchronization mechanism to avoid data corruption
  -                            when using multiple OJB servers.
  -                        </li>
  -                    </ul>
  +                    Support of <link href="site:object-cache/distributed-cache">distributed
caches</link>.
                   </li>
                   <li>
                       Comes along with fully functional demo applications running against
  
  
  
  1.13      +5 -2      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.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- site.xml	12 May 2004 00:48:27 -0000	1.12
  +++ site.xml	12 May 2004 16:06:11 -0000	1.13
  @@ -142,12 +142,15 @@
               </metadata>
               <deployment label="Deployment" href="deployment.html" description="">
                   <additional-jars href="#additional-jars"/>
  +                <j2ee-server href="#j2ee-server"/>
               </deployment>
               <connection label="Connection handling" href="connection.html" description="">
                   <connection-pooling href="#connection-pooling"/>
                   <obtain-connection href="#obtain-connection"/>
               </connection>
  -            <object-cache label="Object Cache" href="objectcache.html" description=""/>
  +            <object-cache label="Object Cache" href="objectcache.html" description="">
  +                <distributed-cache href="#distributed-cache"/>
  +            </object-cache>
               <sequence-manager label="Sequence Manager" href="sequencemanager.html" description=""/>
               <lock-manager label="Lock Manager" href="lockmanager.html" description="">
                   <distributed-locking href="#distributed-locking"/>
  
  
  

---------------------------------------------------------------------
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