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 release-notes.txt
Date Wed, 25 Feb 2004 01:23:23 GMT
arminw      2004/02/24 17:23:23

  Modified:    .        release-notes.txt
  Log:
  update release notes
  
  Revision  Changes    Path
  1.34      +21 -4     db-ojb/release-notes.txt
  
  Index: release-notes.txt
  ===================================================================
  RCS file: /home/cvs/db-ojb/release-notes.txt,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -r1.33 -r1.34
  --- release-notes.txt	17 Jan 2004 17:02:07 -0000	1.33
  +++ release-notes.txt	25 Feb 2004 01:23:23 -0000	1.34
  @@ -17,16 +17,29 @@
   NOTES:
   - No support for HSQLDB 1.7.2RC1 yet
   - No support for Torque 3.1 yet
  -- Add new PersistenceBrokerFactory implementation for use in managed environments when
only the
  +
  +- Add new PersistenceBrokerFactory implementation for use in managed environments when
*only* the
   PB-api was used and participation in JTA transaction via Synchronization interface is needed.
  +
   - Add new configuration property 'autoSync' to ObjectCacheDefaultImpl. Used to enable a
simple
   synchronization mechanism to keep cache in sync with DB
   
   CHANGES:
  +- fix bug in internal table OJB_HL_SEQ, column type of MAX_ID was INTEGER but
  +needs BIGINT to support Long on java side
  +
  +- no longer throw an exception when calling abortTransaction more than one time
  +or an internal rollback (by ConnectionManager on the used connection) was already done
  +
   - Add object-cache tag in standard jdbc-connection-descriptor in repository_database.xml
   to enable new 'autoSync' property of ObjectCacheDefaultImpl for all operations made by
   this DB connection
  -- Allow infinite lifetime of cached objects in ObjectCacheDefaultImpl
  +
  +- Allow infinite lifetime of cached objects in ObjectCacheDefaultImpl (handle with care
;-))
  +
  +- odmg-api implementation, disable restore of transient objects on transaction abort,
  +because we can't really restore the whole object with all references
  +
   - now using ANTLR 2.7.2 and Unicode support in OQL queries
   - now using ANT 1.6.0
   
  @@ -57,9 +70,13 @@
   
   - The bogus ODMG Distributed Lockmanagement feature has been replaced by a new
     Servlet based LockServer. Transaction isolation should now work properly even
  -  accross a cluster of JVMs. 
  +  accross a cluster of JVMs.
   
   KNOWN ISSUES:
  +- odmg-api: It is not possible to exchange objects in 1:n references.
  +E.g. two objects with 1:n reference, each with one reference object, obj_1{ref_1}
  +and obj_2{ref_2}. Lock objects and exchange the references in collection obj_1{ref_2}
  +and obj_2{ref_1} and commit.
   
   
   ---------------------------------------------------------------------
  
  
  

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