db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From t...@apache.org
Subject cvs commit: db-ojb/xdocs features.xml status.xml
Date Sat, 13 Dec 2003 21:49:15 GMT
thma        2003/12/13 13:49:15

  Modified:    xdocs    features.xml status.xml
  Log:
  update status information
  
  Revision  Changes    Path
  1.10      +12 -5     db-ojb/xdocs/features.xml
  
  Index: features.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/xdocs/features.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- features.xml	1 Jul 2003 07:28:13 -0000	1.9
  +++ features.xml	13 Dec 2003 21:49:15 -0000	1.10
  @@ -80,19 +80,23 @@
         Sequence-Managing. The SequenceManager is aware of extents
         and maintains uniqueness of ids accross any number of tables.
         Sequence Numbering can be declared in the mappping repository.
  +      <br/>
  +      Native Database Sequence Numbering is also supported.
       </li>
       <li>Reusing Prepared Statements, internal connection pooling.</li>
       <li>
         Integrates smoothly in controlled environments like EJB containers
         (wrt. SecurityManagers and JNDI based Datasources).
       </li>
  +	<li>
  +	  Full JTA and JCA Integration.
  +	</li>
       <li>
         Support for <a href="query.html#prefetched relationships">prefetched relationships</a>
         to minimize the number of queries.
       </li>
       <li>
  -      ODMG compliant API, a Tutorial, and TestCases are included
  -      (see package test.ojb.odmg) <br/>
  +      ODMG compliant API, a Tutorial, and TestCases are included. <br/>
         <font COLOR="#ff0000">Important notes: </font>
       </li>
       <li>
  @@ -104,9 +108,12 @@
         properly. To achieve safe transaction isolation client application
         must use explicit lock acquisition.</FONT>
       </li>
  +	<li>
  +	  JDO 1.0.1 compliant API, a Tutorial, and TestCases are included.
  +	</li>    
       <li>
  -      Scalable client / server architecture that allows to build
  -      massively distributed systems.
  +      Scalable architecture that allows to build
  +      massively distributed and clustered systems.
       </li>
       <li>
         Distributed Lockmanagement supporting four pessimistic
  @@ -124,7 +131,7 @@
         HSQLDB.
       </li>
       <li>
  -      Quality assurance taken seriously: More than 120 JUnit-TestCases for
  +      Quality assurance taken seriously: More than 500 JUnit-TestCases for
         regression tests. JUnit tests integrated into the build scripts.
       </li>
       <li>Provides Log4J logging facilities.</li>
  
  
  
  1.6       +11 -33    db-ojb/xdocs/status.xml
  
  Index: status.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/xdocs/status.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- status.xml	4 May 2003 12:07:44 -0000	1.5
  +++ status.xml	13 Dec 2003 21:49:15 -0000	1.6
  @@ -11,7 +11,9 @@
   <section name="news">
   	<ul>
   		<li>
  -			The 1.0 release candidate RC3 is out. The 1.0 final release is in sight!
  +			The 1.0 release candidate RC5 is out.
  +			If we do not discover serious problems with this build it will
  +			relabeled as the final 1.0 version within two weeks.
   		</li>
   	</ul>
   
  @@ -20,46 +22,22 @@
   
   <section name="status">
   <P>
  -Only major implemented features are listed here. A <A HREF="features.html">complete
  -list features is here</A>.
  +Only major implemented features are listed here. A <A HREF="features.html">more 
complete
  +list of features is here</A>.
   </P>
   <UL>
  -    <li>The PersistenceBroker is quite
  -    stable, only minor Modfications and bug fixes are to be expected.</li>
  +    <li>The PersistenceBroker interface is stable.</li>
       <li>The ODMG interface is stable
       <br/><FONT COLOR="#ff0000">Important notes: <br/>OQL is currently
not
       fully implemented. (Aggregations and Method Invocations)<br/>ODMG
       implicit locking is partly implemented but does currently not
       maintain transaction isolation properly. To achieve safe transaction
       isolation client application must use explicit lock acquisition.</FONT></li>
  -</UL>
  -
  -<UL>
  -    <li>Distributed persistent lock handling implemented.</li>
  -    <li>built in support for major RDBMS (Oracle, DB2, mySQL,
  -    PostgresSQL, etc.)</li>
  -    <li>m-n mapping support</li>
  -    <li>automatic assignment of foreign key values</li>
  -    <li>provide distributed Meta-Object Protocol access through
  -    PersistenceBroker API</li>
  -    <li>complete query api (incl. Joins)</li>
  -    <li>support for optimistic locking</li>
  -    <li>administrative console for PersistenceBrokerServer</li>
  -    <li>cleanup the Repository DTD</li>
  -    <li>thorough revision of documentation</li>
  -    <li>JTA / JCA integration</li>
  -</UL>
  -</section>
  -<section name="to do">
  -<P>
  -	Only major features are listed.
  -</P>
  -<UL>
  -    <li><B>For release 2.0</B></li>
  -    <UL>
  -        <li>JDO compliant interface</li>
  -        <li>Graphical tool for building Object / Relational mappings</li>
  -    </UL>
  +    <li>By providing a plugin to the SUN JDO Reference Implementation we provide
  +    a complete JDO 1.0.1 O/R mapping tool.
  +    A complete Apache licensed JDO implementation is scheduled for OJB 2.0.
  +    </li>
  +	<li>The OTM Object Transaction Manager API is also stable with this release.</li>
   </UL>
   
   </section>
  
  
  

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