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/src/doc/forrest/src/documentation/content/xdocs/docu/guides objectcache.xml
Date Sat, 12 Mar 2005 01:07:25 GMT
arminw      2005/03/11 17:07:25

  Modified:    src/doc/forrest/src/documentation/content/xdocs/docu/guides
                        Tag: OJB_1_0_RELEASE objectcache.xml
  fix typo
  minor changes
  Revision  Changes    Path
  No                   revision
  No                   revision   +16 -15    db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/objectcache.xml
  Index: objectcache.xml
  RCS file: /home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/objectcache.xml,v
  retrieving revision
  retrieving revision
  diff -u -r1.1.2.3 -r1.1.2.4
  --- objectcache.xml	7 Feb 2005 20:43:08 -0000
  +++ objectcache.xml	12 Mar 2005 01:07:25 -0000
  @@ -476,17 +476,16 @@
                       <link href="ext:api/cache-two-level">ObjectCacheTwoLevelImpl</link>
is a two level
                       <link href="ext:api/cache-interface">ObjectCache</link>
implementation with a transactional
  -                    session- and an shared application-cache part.
  +                    session- and a shared application-cache part.
                       The first level is a transactional session
  -                    cache which cache objects till
  +                    cache that cache objects till
                       <link href="ext:api/persistence-broker">PersistenceBroker</link>#close()
                       or if a PB-tx is running till <code>#abortTransaction()</code>
  -                    <code>#commitTransaction()</code>.
  +                    <code>#commitTransaction()</code> was called.
  -                    On commit all objects from the session cache will be pushed to the
application cache
  -                    (more precisely, only objects written to database till the PB-tx).
  +                    On commit all objects reside in the session cache will be pushed to
the application cache.
                       If objects be new materialized from the database (e.g. when achieve
a query), the full materialized
                       objects will be pushed immediately to the application cache (more precisely,
if the application
  @@ -495,19 +494,21 @@
                       The second level cache can be specified with the <em>applicationCache</em>
property. Properties of
                       the specified application cache are allowed too. Here is an example
how to use the two level
  -                    cache with <code>ObjectCacheDefaultImpl</code> as second
level cache.
  +                    cache with <link href="#defaultImpl"><code>ObjectCacheDefaultImpl</code></link>
as second level cache.
   <object-cache class="org.apache.ojb.broker.cache.ObjectCacheTwoLevelImpl">
  +    <!-- meaning of attributes, please see docs section "Caching" -->
  +    <!-- common attributes -->
       <attribute attribute-name="cacheExcludes" attribute-value=""/>
  -    <attribute attribute-name="applicationCache" attribute-value=
  -    <attribute attribute-name="copyStrategy" attribute-value=
  -    <!-- properties for used application cache - ObjectCacheDefaultImpl -->
  +    <!-- ObjectCacheTwoLevelImpl attributes -->
  +    <attribute attribute-name="applicationCache"
  +        attribute-value="org.apache.ojb.broker.cache.ObjectCacheDefaultImpl"/>
  +    <attribute attribute-name="copyStrategy"
  +        attribute-value="org.apache.ojb.broker.cache.ObjectCacheTwoLevelImpl$CopyStrategyImpl"/>
  +    <!-- ObjectCacheDefaultImpl attributes -->
       <attribute attribute-name="timeout" attribute-value="900"/>
  -    <attribute attribute-name="autoSync" attribute-value="false"/>
  +    <attribute attribute-name="autoSync" attribute-value="true"/>
       <attribute attribute-name="cachingKeyType" attribute-value="0"/>
       <attribute attribute-name="useSoftReferences" attribute-value="true"/>
  @@ -515,7 +516,7 @@
                       The most important characteristic of the two-level cache is that all
objects put to or read from
                       the application cache are copies of the target object, so the cached
objects never could be
                       corrupted by the user when changing fields, because all operations
done on copies of
  -                    objects cached in application cache (in contrast to
  +                    objects cached in the application cache (in contrast to
                       <link href="#defaultImpl">ObjectCacheDefaultImpl</link>).

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

View raw message