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 release-notes.txt
Date Thu, 08 Jan 2004 15:31:10 GMT
thma        2004/01/08 07:31:10

  Modified:    .        release-notes.txt
  Log:
  add some more notes..
  
  Revision  Changes    Path
  1.30      +18 -7     db-ojb/release-notes.txt
  
  Index: release-notes.txt
  ===================================================================
  RCS file: /home/cvs/db-ojb/release-notes.txt,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- release-notes.txt	4 Jan 2004 18:29:16 -0000	1.29
  +++ release-notes.txt	8 Jan 2004 15:31:10 -0000	1.30
  @@ -15,20 +15,21 @@
    -
   
   NOTES:
  - -
  + - No support for HSQLDB 1.7.2RC1 yet
  + - No support for Torque 3.1 yet
   
   CHANGES:
   - Add new configuration property 'useAutoSync' to ObjectCacheDefaultImpl
   - Add object-cache tag in standard jdbc-connection-descriptor in repository_database.xml
   to enable new 'useAutoSync' property of ObjectCacheDefaultImpl
   - Allow infinite lifetime of cached objects in ObjectCacheDefaultImpl
  -
  +- now using ANTLR 1.7.2 and Unicode support in OQL queries
   
   BUG FIXES:
   
  -Please refer to our Bug tracking site under
  -http://scarab.werken.com/scarab/issues/id/OJBxxx to see details for a bug
  -with id OJBxxx.
  +Please refer to our Bug tracking site (http://issues.apache.org/scarab/servlet/scarab/)

  +under http://issues.apache.org/scarab/servlet/scarab/issues/id/OJBxxx 
  +to see details for a bug with id OJBxxx.
   
   - fix bug in MetadataManager, when 'per thread changes' is enabled and many different
   DescriptorRepository instances were used, gc can't collect unused instances because
  @@ -49,7 +50,17 @@
   re-loaded within tx, but iteration over the list values was done outside of the tx
   
   KNOWN ISSUES:
  -
  +- The ODMG Distributed Lockmanagement feature seems to be buggy. 
  +  (LockMapClass=org.apache.ojb.odmg.locking.PersistentLockMapImpl)
  +  Currently locks are written to the db in the same transaction as the 
  +  business logic operations. Thus locks may not be visible outside the current
  +  business transaction.
  +  We were not able to fix this yet as compley situations in managed transaction
  +  environments must be taken in a count.
  +  We will ship a replacement of the buggy LockManagement asap.
  +  The InMemory Lockmanagement 
  +  (LockMapClass=org.apache.ojb.odmg.locking.InMemoryLockMapImpl)
  +  is not affected.
   
   
   ---------------------------------------------------------------------
  
  
  

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