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/xdocs sequencemanager.xml objectcache.xml deployment.xml
Date Wed, 03 Sep 2003 18:51:35 GMT
arminw      2003/09/03 11:51:35

  Modified:    xdocs    sequencemanager.xml objectcache.xml deployment.xml
  Log:
  update doc
  
  Revision  Changes    Path
  1.14      +16 -15    db-ojb/xdocs/sequencemanager.xml
  
  Index: sequencemanager.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/xdocs/sequencemanager.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- sequencemanager.xml	9 Aug 2003 00:27:52 -0000	1.13
  +++ sequencemanager.xml	3 Sep 2003 18:51:35 -0000	1.14
  @@ -206,35 +206,35 @@
                                       attribute-value="true"/>
   </sequence-manager>
   ]]></source>
  -
  -With the property <code>grabSize</code> you set the size of the assigned ids
  +</p>
  +<p>
  +With property <code>grabSize</code> you set the size of the assigned ids
   (default was 20).
  -<br/>
  +</p>
  +
  +<p>
   If property <code>globalSequenceId</code> was set <code>true</code>
you will
   get global unique ids over all persistent objects. Default was <code>false</code>.
   <br/>
   The attribute <code>globalSequenceStart</code> define the start value of the
   global id generation (default was 10000).
  -<br/>
  +</p>
  +<p>
  +This sequence manager implementation supports user defined <i>sequence-names</i>
  +to manage the sequences.
   The attribute <code>autoNaming</code> define if sequence names should be build
   automatic if none found in <code>field-descriptor</code>.
  +<br/>
   If set 'true' OJB try to build a
   sequence name automatic if none found in field-descriptor
   and set this name as <code>sequence-name</code>
  -in field-descriptor. If set 'false' OJB throws an exception
  +in field-descriptor (see <a href="#sequenceName">more</a>).
  +If set 'false' OJB throws an exception
   if none sequence name was found in field-descriptor (default was 'true').
   </p>
   <p>
  -This sequence manager implementation supports user defined <i>sequence-names</i>
  -to manage the sequences (see <a href="#sequenceName">more</a>) or if not
  -set in <code>field-descriptor</code> it is done automatic.
  -</p>
  -<p>
   Limitations:
  -<br/>- do not use when connections were associated with a
  -transaction, e.g. when using DataSources from an j2ee conform application server
  -<br/>- do not use if other entities use database based sequencing
  -or database will be updated by other applications
  +<br/>- superfluously to mention, do not use if database will be updated by other
applications
   </p>
   
   <br/>
  @@ -303,7 +303,8 @@
   to define a <b>sequence-name</b> <code>field-descriptor</code>
attribute
   in the repository file for each autoincrement/pk field. If you don't
   specify a sequence name, the sequence manager try to
  -build a extent-aware sequence name on its own.
  +build a extent-aware sequence name on its own - except you set attribute
  +<code>autoNaming</code> to 'false', then an exception will be thrown.
   <br/>
   Keep in mind that in this case you are responsible to be aware of extents.
   Thus you have to use the same <code>sequence-name</code> attribute value
  
  
  
  1.6       +9 -0      db-ojb/xdocs/objectcache.xml
  
  Index: objectcache.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/xdocs/objectcache.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- objectcache.xml	9 Aug 2003 00:24:17 -0000	1.5
  +++ objectcache.xml	3 Sep 2003 18:51:35 -0000	1.6
  @@ -18,6 +18,7 @@
       <li><a href="#How to change the used ObjectCache implementation">How to
change the used ObjectCache implementation</a></li>
       <li><a href="#Alternative cache implementations">Alternative cache implementations</a></li>
       <li><a href="#Implement your own cache">Implement your own cache</a></li>
  +    <li><a href="#Distributed ObjectCache implementations">Distributed ObjectCache
implementations</a></li>
       <li><a href="#"></a></li>
       <li><a href="#CacheFilter feature">CacheFilter feature</a>
           <ul>
  @@ -214,6 +215,14 @@
   implemented something interesting, just contact me.</p>
   </subsection>
   
  +
  +
  +
  +    <subsection name="Distributed ObjectCache implementations">
  +    <p>
  +
  +    </p>
  +    </subsection>
   
   
   
  
  
  
  1.27      +12 -8     db-ojb/xdocs/deployment.xml
  
  Index: deployment.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/xdocs/deployment.xml,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- deployment.xml	9 Aug 2003 00:17:04 -0000	1.26
  +++ deployment.xml	3 Sep 2003 18:51:35 -0000	1.27
  @@ -384,20 +384,24 @@
   JTATransactionManagerClass=
   org.apache.ojb.otm.transaction.factory.JBossTransactionManagerFactory
   ]]></source>
  +<p>
   Using the PB-api it is recommended to use
   <br/><code>ObjectCacheClass=org.apache.ojb.broker.cache.ObjectCachePerBrokerImpl</code>
   <br/>or
   <br/><code>ObjectCacheClass=org.apache.ojb.broker.cache.ObjectCacheEmptyImpl</code>.
   <br/>
  -When using the ODMG-api and the application server is not clustered it's also possible
  -to use all other implementations. The JCS based <code>ObjectCache</code> implementations
  -should also be able to work in distributed environments
  -(see <a href="http://jakarta.apache.org/turbine/jcs/">JCS docs</a>).
  +because PB-api do not use JTA-Synchronization like ODMG-api implementation.
   </p>
  -<p>
  -
  +When using the ODMG-api and the application server is not clustered it's possible
  +to use all <code>ObjectCache</code> implementations. In clustered environments
you
  +need a distributed ObjectCache or you should use a local/empty cache like
  +<br/><code>ObjectCacheClass=org.apache.ojb.broker.cache.ObjectCachePerBrokerImpl</code>
  +<br/>or
  +<br/><code>ObjectCacheClass=org.apache.ojb.broker.cache.ObjectCacheEmptyImpl</code>.
  +More info you can find in
  +<a href="howto-work-with-clustering.html">clustering</a> and
  +<a href="objectcache.html">ObjectCache</a> topic.
   </p>
  -
   
   <p>
   <b>7. Declare datasources in the repository (repository_database) file</b>
  
  
  

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