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 Mon, 20 Sep 2004 13:43:32 GMT
arminw      2004/09/20 06:43:32

  Modified:    .        Tag: OJB_1_0_RELEASE release-notes.txt
  Log:
  update notes
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.54.2.12 +22 -19    db-ojb/release-notes.txt
  
  Index: release-notes.txt
  ===================================================================
  RCS file: /home/cvs/db-ojb/release-notes.txt,v
  retrieving revision 1.54.2.11
  retrieving revision 1.54.2.12
  diff -u -r1.54.2.11 -r1.54.2.12
  --- release-notes.txt	16 Sep 2004 12:37:28 -0000	1.54.2.11
  +++ release-notes.txt	20 Sep 2004 13:43:32 -0000	1.54.2.12
  @@ -15,21 +15,24 @@
   
   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
  +  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
  +- ODMG-api improved, up to 30% better performance
   
   CHANGES:
   - !!!In managed enviroments the org.odmg.Transaction#abort() call no longer throws an
  -TransactionAbortedExceptionOJB, instead OJB does internal cleanup and set used
  -JTA-tx to setRollbackOnly if possible. Thus the client does no longer get an RemoteException.
  -The user have to throw an EJBException by himself to notify the client.
  -- Performance of the default RowReader (RoxReaderDefaultImpl) was improved, when mapping
  -several classes to the same table ("ojb-conrete class" feature), now only the fields of
the
  -associated class were performed in RowReader instead invoking all fields of the table used
by
  -the mapped classes.
  +  TransactionAbortedExceptionOJB, instead OJB does internal cleanup and set used
  +  JTA-tx to setRollbackOnly if possible. Thus the client does no longer get an RemoteException.
  +  The user have to throw an EJBException by himself to notify the client.
  +- Performance of the default RowReader (RowReaderDefaultImpl) was improved, when mapping
  +  several classes to the same table ("ojb-conrete class" feature), now only the fields
of the
  +  associated class were performed in RowReader instead invoking all fields of the table
used by
  +  the mapped classes.
  +- Introduce new locking-package in kernel api, adapt odmg-locking stuff and remove unused
  +  classes from org.apache.ojb.odmg.locking package.
   
   BUG FIXES:
   Please refer to our Bug tracking site (http://issues.apache.org/scarab/servlet/scarab/)
  @@ -37,15 +40,15 @@
   to see details for a bug with id OJBxxx.
   
   - 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.
  +  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.
  +  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()
  +  Synchronization#afterCompletion(int status) was called by the JTA-TxManager instead doing
all this
  +  stuff in #beforeCompletion()
   - odmg-api: Assign FK for 1:1 relations when persistent objects are written to DB, instead
when objects
  -were locked.
  +  were locked.
   
   KNOWN ISSUES:
   - odmg-api: If a user exchange already existing objects in 1:n references without changing
the size
  
  
  

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