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 Tue, 22 Mar 2005 18:15:53 GMT
arminw      2005/03/22 10:15:53

  Modified:    .        Tag: OJB_1_0_RELEASE release-notes.txt
  Log:
  update notes, odmg fixed multi table mapping
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.54.2.39 +7 -6      db-ojb/release-notes.txt
  
  Index: release-notes.txt
  ===================================================================
  RCS file: /home/cvs/db-ojb/release-notes.txt,v
  retrieving revision 1.54.2.38
  retrieving revision 1.54.2.39
  diff -u -r1.54.2.38 -r1.54.2.39
  --- release-notes.txt	18 Mar 2005 21:40:09 -0000	1.54.2.38
  +++ release-notes.txt	22 Mar 2005 18:15:53 -0000	1.54.2.39
  @@ -162,7 +162,8 @@
     will not be updated. This is fixed.
   - odmg-api: Fixed: Creation of m:n relation only works when objects created step by step
(or use PB-api
     as workaround), persist a whole object graph seems not to work proper. This is fixed.
  -
  +- odmg-api: Fixed: Mapping classes on multiple joined tables was not supported in
  +  ODMG-API implementation. This is fixed (!except the known issue when Query or refer to
a base class).
   
   KNOWN ISSUES:
   - Auto-Detection for insert/update objects checks to avoid DB queries the PK fields of
the object.
  @@ -177,12 +178,12 @@
     a 1:n reference 'employees' to a base class Employee and class Manager extends Employee,
     then 'employees' only contains objects of type Employee even if the real type was Manager.
     See in OJB test suite ...broker.InheritanceMultipleTableTest#testInheritancedObjectsInCollectionReferences
  +  Same problem occur when query the base class, then OJB only returns objects of base type
instead
  +  the real type.
   - Managed Environment: When run OJB in managed environment and using PBStateListener, the
call of
     PBStateListener#beforeClose(PBStateEvent event) is made twice when
  -  a PB instance was closed in a JTA-tx (for the first time when PB.close() was called in
bean on the PB handle
  -  , second time when the JTA-tx completes)
  -- odmg-api: Mapping classes on multiple joined tables was not supported in
  -  ODMG-API implementation (PB-api support this kind of inheritance with restrictions -
see known issues).
  +  a PB instance was closed in a JTA-tx (for the first time when PB.close() was called
  +  in bean on the PB handle, second time when the JTA-tx completes)
   - otm-api: The OTM API has a known caching issue and should not be considered for code
used
     in production environments. The future of the OTM layer will be subject for discussion
on the
     OJB developers list, if you are using it - please subscribe to ojb-dev and make your
voice heard.
  
  
  

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