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 deployment.xml
Date Fri, 23 Jan 2004 23:38:07 GMT
arminw      2004/01/23 15:38:07

  Modified:    xdocs    deployment.xml
  Log:
  update jboss deployment description
  
  Revision  Changes    Path
  1.30      +29 -10    db-ojb/xdocs/deployment.xml
  
  Index: deployment.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/xdocs/deployment.xml,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- deployment.xml	9 Jan 2004 19:29:36 -0000	1.29
  +++ deployment.xml	23 Jan 2004 23:38:07 -0000	1.30
  @@ -243,9 +243,10 @@
   <P>
       There are some topics you should examine very carefully:
       <ul>
  -        <li><b>Caching</b>: </li>
  -        <li><b>Connection handling</b></li>
  -        <li><b>Locking</b></li>
  +        <li><b>Connection handling:</b> Lookup DataSource from your AppServer,
only these
  +        connections will be enlisted in running transactions</li>
  +        <li><b>Caching:</b> Do you need distributed caching?</li>
  +        <li><b>Locking:</b> Do you need distributed locking (e.g. when
using odmg-api)?</li>
       </ul>
   </P>
   
  @@ -277,7 +278,7 @@
       that depends on the used environment. In JBoss you can use <code>mbean</code>
classes
       to do that <code>org.apache.ojb.jboss.PBFactory</code> and <code>org.apache.ojb.jboss.ODMGFactory</code>.
   <br/>
  -Let JBoss know about the new mbeans, so declare tem in a <code>jboss-service.xml</code>
file:
  +Let JBoss know about the new mbeans, so declare them in a <code>jboss-service.xml</code>
file:
   <source><![CDATA[
   <?xml version="1.0" encoding="UTF-8"?>
   
  @@ -407,7 +408,8 @@
   Don't use this setting in conjunction with the ODMG-api.
   </p>
   <p>
  -Your OJB.properties file need the following additional settings:
  +Your OJB.properties file need the following additional settings to work within
  +managed environments (apply to <b>all</b> used api):
   <source><![CDATA[
   ...
   ConnectionFactoryClass=
  @@ -424,7 +426,7 @@
   </p>
   
   <p>
  -<b>7. Declare datasources in the repository (repository_database) file and do additional
configuration</b>
  +<b>7a. Declare datasources in the repository (repository_database) file and do additional
configuration</b>
   <br/>
   Do only use <code>DataSource</code> from the application server to connect
your databases.
   <br/>
  @@ -467,8 +469,12 @@
       In managed environments you can't use the default sequence manager (SequenceManagerHighLowImpl)
       of OJB. For alternative sequence manager implemetation <a href="sequencemanager.html">see
here</a>.
   </p>
  +
  +
   <p>
  -Most important thing is cache synchronization with the database.
  +<b>7b. Take care of caching</b>
  +<br/>
  +Very important thing is cache synchronization with the database.
   When using the ODMG-api or PB-api (with <a href="#jboss-ojb.properties">special PBF
(see 6.)</a> setting)
   it's possible to use all <code>ObjectCache</code> implementations as long as
OJB doesn't run
   in a clustered mode. When the <code>ObjectCacheDefaultImpl</code> cache implementation
was used it's
  @@ -479,6 +485,8 @@
   <br/><code>ObjectCacheClass=org.apache.ojb.broker.cache.ObjectCachePerBrokerImpl</code>
   <br/>or
   <br/><code>ObjectCacheClass=org.apache.ojb.broker.cache.ObjectCacheEmptyImpl</code>.
  +The cache is pluggable, so you can write your own ObjectCache implementation to accomplish
  +your expectations.
   <p>
   More info you can find in
   <a href="howto-work-with-clustering.html">clustering</a> and
  @@ -486,8 +494,19 @@
   </p>
   </p>
   
  +
  +<p>
  +<b>7c. Take care of locking</b>
  +<br/>
  +If the used api supports <tt>Object Locking</tt> (e.g. ODMG-api), in clustered
environments
  +(OJB run on different AppServer nodes) a distributed lock management is necessary.
  +<br/>
  +
  +</p>
  +
  +
   <p>
  -<b>7b. How to deploy ojb test hsqldb database to jboss</b>
  +<b>[7d. How to deploy ojb test hsqldb database to jboss]</b>
   <br/>
   After creating the database with
   <code>bin\build.bat prepare-testdb</code> or <code>bin/build.sh prepare-testdb</code>.
  @@ -531,7 +550,7 @@
   </p>
   
   <p>
  -<b>OJB logging within JBoss</b><br/>
  +<b>8c. OJB logging within JBoss</b><br/>
   Jboss use <a href="http://jakarta.apache.org/log4j">log4j</a> as standard logging
api.
   <br/>
   In summary, to use log4j logging with OJB within jBoss,
  
  
  

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