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, 15 Jun 2004 11:44:36 GMT
arminw      2004/06/15 04:44:36

  Modified:    src/test/org/apache/ojb/odmg M2NTest.java
               src/test/org/apache/ojb repository_junit_odmg.xml
                        repository_junit_reference.xml
               .        release-notes.txt
  Log:
  fix test bug, use non-removalaware collections in m:n tests
  
  Revision  Changes    Path
  1.3       +1 -5      db-ojb/src/test/org/apache/ojb/odmg/M2NTest.java
  
  Index: M2NTest.java
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/test/org/apache/ojb/odmg/M2NTest.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- M2NTest.java	5 May 2004 13:04:58 -0000	1.2
  +++ M2NTest.java	15 Jun 2004 11:44:36 -0000	1.3
  @@ -361,16 +361,12 @@
   
       public void testRemoveAssociation() throws Exception
       {
  -        // TODO: Expect that objects removed from an m:n collection only be removed from
indirection table
  -        if(ojbSkipKnownIssueProblem()) return;
           prepareAutoUpdateDeleteSettings(false);
           doTestRemoveAssociation();
       }
   
       public void testRemoveAssociationWithProxy() throws Exception
       {
  -        // TODO: Expect that objects removed from an m:n collection only be removed from
indirection table
  -        if(ojbSkipKnownIssueProblem()) return;
           changeMovieCollectionDescriptorTo(true, LINK, LINK, true);
           changeActorCollectionDescriptorTo(true, LINK, LINK, false);
           doTestRemoveAssociation();
  
  
  
  1.11      +2 -1      db-ojb/src/test/org/apache/ojb/repository_junit_odmg.xml
  
  Index: repository_junit_odmg.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/test/org/apache/ojb/repository_junit_odmg.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- repository_junit_odmg.xml	11 May 2004 11:55:57 -0000	1.10
  +++ repository_junit_odmg.xml	15 Jun 2004 11:44:36 -0000	1.11
  @@ -1125,6 +1125,7 @@
   
           <collection-descriptor
               name="actors"
  +            collection-class="org.apache.ojb.broker.util.collections.ManageableArrayList"
               element-class-ref="org.apache.ojb.odmg.M2NTest$Actor"
               auto-retrieve="false"
               auto-update="false"
  
  
  
  1.15      +2 -1      db-ojb/src/test/org/apache/ojb/repository_junit_reference.xml
  
  Index: repository_junit_reference.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/test/org/apache/ojb/repository_junit_reference.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- repository_junit_reference.xml	12 Jun 2004 13:43:12 -0000	1.14
  +++ repository_junit_reference.xml	15 Jun 2004 11:44:36 -0000	1.15
  @@ -1361,6 +1361,7 @@
   
           <collection-descriptor
               name="actors"
  +            collection-class="org.apache.ojb.broker.util.collections.ManageableArrayList"
               element-class-ref="org.apache.ojb.broker.M2NTest$Actor"
               auto-retrieve="false"
               auto-update="false"
  
  
  
  1.48      +8 -8      db-ojb/release-notes.txt
  
  Index: release-notes.txt
  ===================================================================
  RCS file: /home/cvs/db-ojb/release-notes.txt,v
  retrieving revision 1.47
  retrieving revision 1.48
  diff -u -r1.47 -r1.48
  --- release-notes.txt	14 Jun 2004 14:37:05 -0000	1.47
  +++ release-notes.txt	15 Jun 2004 11:44:36 -0000	1.48
  @@ -52,15 +52,15 @@
   to see details for a bug with id OJBxxx.
   
   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.
  +- odmg-api: If a user exchange already existing objects in 1:n references, the main object
  +will not become dirty and the FK values of the exchanged objects will not be updated.
  +E.g. two objects obj_1 anf obj_2 with 1:n reference to ref objects, each with one
  +existing/persistent 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 --> FK values of ref_1 and ref_2 will not be updated.
   
   - odmg-api: Creation of m:n relation only works when objects created step by step (or use
PB-api
  -as workaround), persist a whole object graph doesn't work. On delete of collection objects
from a m:n relation
  -objects will be deleted from the indirection table and (unexpected behaviour) from the
referenced
  -table too.
  +as workaround), persist a whole object graph seems not to work proper.
   
   - ReportQueries should not be used with columns referencing Classes with extents:
   
  
  
  

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