[jboss-cvs] JBossCache/docs/PojoCache/en/modules ...

[Ben Wang]

  User: bwang   
  Date: 06/09/29 05:46:30

  Modified:    docs/PojoCache/en/modules  configuration.xml
  Log:
  Fixed typos.
  
  Revision  Changes    Path
  1.5       +7 -5      JBossCache/docs/PojoCache/en/modules/configuration.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: configuration.xml
  ===================================================================
  RCS file: /cvsroot/jboss/JBossCache/docs/PojoCache/en/modules/configuration.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -b -r1.4 -r1.5
  --- configuration.xml	27 Sep 2006 06:49:42 -0000	1.4
  +++ configuration.xml	29 Sep 2006 09:46:30 -0000	1.5
  @@ -20,9 +20,15 @@
      <sect1>
         <title>Passivation configuration</title>
         <para>A user can also configure the underlying Cache to activate the passivation. Passivation is feature
  -         needed to keep the VM memory compact. In JBoss Cache, it is done via combincation of eviction
  +         needed to keep the VM memory compact. In JBoss Cache, it is done via combination of eviction
            policy and cache loader. That is, when a node is evicted from Cache, it will store into the cache
            loader. When the node is requested again, it will be loaded from the store and stored into memory.
  +         </para><para>There is a restriction, however. Since we use the "flat space" physical POJO mapping, there are
  +         two places that has POJO information. One is under the regular String ID that the user specifies, and
  +         the other is located under <code>/__JBossInteranl__</code>. Therefore, to be consistent, when you specify
  +         the eviction region, you can only specify one global region (i.e., <code>/_default_</code> region).
  +            This way, when the nodes associated with the POJO is passivated, they will do so across the whole
  +         region.
            Below is a snippet from a cache configuration xml
         illustrating how the eviction policy along with cache loader can be configured. Please note that this is
            simply an aspect of the underlying Cache. That is, PojoCache layer is agnostic to this behavior.
  @@ -36,10 +42,6 @@
             &lt;attribute name="maxNodes"&gt;5000&lt;/attribute&gt;
             &lt;attribute name="timeToLiveSeconds"&gt;3&lt;/attribute&gt;
         &lt;/region&gt;
  -      &lt;region name="/org/jboss/test/data"&gt;
  -          &lt;attribute name="maxNodes"&gt;100&lt;/attribute&gt;
  -          &lt;attribute name="timeToLiveSeconds"&gt;3&lt;/attribute&gt;
  -      &lt;/region&gt;
      &lt;/config&gt;
   &lt;/attribute&gt;