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 Thu, 16 Sep 2004 12:37:28 GMT
arminw      2004/09/16 05:37:28

  Modified:    .        Tag: OJB_1_0_RELEASE release-notes.txt
  Log:
  add new note
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.54.2.11 +10 -2     db-ojb/release-notes.txt
  
  Index: release-notes.txt
  ===================================================================
  RCS file: /home/cvs/db-ojb/release-notes.txt,v
  retrieving revision 1.54.2.10
  retrieving revision 1.54.2.11
  diff -u -r1.54.2.10 -r1.54.2.11
  --- release-notes.txt	15 Sep 2004 09:30:24 -0000	1.54.2.10
  +++ release-notes.txt	16 Sep 2004 12:37:28 -0000	1.54.2.11
  @@ -14,7 +14,12 @@
   -
   
   NOTES:
  --
  +- If you plan to use OJB with an J2SE version older than 1.4, then you have to
  +replace the Geronimo jars with the corresponding ones from Sun's J2EE SDK. This
  +is because Geronimo is a J2EE 1.4 implementation and thus dependant upon
  +J2SE 1.4. Use instead the version of Sun's J2EE reference implementation that
  +correspond to your J2SE version. E.g. for J2SE 1.3 use the J2EE 1.3 SDK which
  +you can get from here: http://java.sun.com/j2ee/1.3/index.jsp
   
   CHANGES:
   - !!!In managed enviroments the org.odmg.Transaction#abort() call no longer throws an
  @@ -33,6 +38,9 @@
   
   - Fix bug in SequenceManagerNativeImpl used to support DB identity columns, make counter
for
   temporary keys static to prevent lock not granted exceptions on insert of new objects.
  +- odmg-api: if within a transaction the client returns a different instance of an already
  +locked object (e.g. serialized through network) method tx.lock and tx.markDirty do not
  +replace the already locked object instance by the new one. Now it will do so.
   - odmg-api: In managed environment odmg-api does clenup internal stuff (cache, locking)
when
   Synchronization#afterCompletion(int status) was called by the JTA-TxManager instead doing
all this
   stuff in #beforeCompletion()
  
  
  

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