You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by ar...@apache.org on 2005/04/03 04:40:57 UTC
cvs commit: db-ojb release-notes.txt
arminw 2005/04/02 18:40:57
Modified: src/test/org/apache/ojb Tag: OJB_1_0_RELEASE OJB.properties
repository_internal.xml
. Tag: OJB_1_0_RELEASE release-notes.txt
Log:
- adapt configuration files (refactoring named object handling, refactoring of DCollection implementations), update release notes
Revision Changes Path
No revision
No revision
1.75.2.7 +4 -6 db-ojb/src/test/org/apache/ojb/OJB.properties
Index: OJB.properties
===================================================================
RCS file: /home/cvs/db-ojb/src/test/org/apache/ojb/OJB.properties,v
retrieving revision 1.75.2.6
retrieving revision 1.75.2.7
diff -u -r1.75.2.6 -r1.75.2.7
--- OJB.properties 29 Mar 2005 18:45:42 -0000 1.75.2.6
+++ OJB.properties 3 Apr 2005 02:40:57 -0000 1.75.2.7
@@ -289,7 +289,7 @@
# interface 'org.apache.ojb.broker.ManageableCollection'.
#
OqlCollectionClass=org.apache.ojb.broker.util.collections.ManageableArrayList
-# OqlCollectionClass=org.apache.ojb.odmg.collections.DListImpl_2
+# OqlCollectionClass=org.apache.ojb.odmg.collections.DListImpl
# OqlCollectionClass=org.apache.ojb.broker.util.collections.ManageableVector
#
# The SqlInLimit entry limits the number of values in IN-sql statement,
@@ -356,12 +356,10 @@
# (e.g. when do a Implementation#newDlist() call)
#
# org.odmg.DList implementation class
-DListClass=org.apache.ojb.odmg.collections.DListImpl_2
-#DListClass=org.apache.ojb.odmg.collections.DListImpl
+DListClass=org.apache.ojb.odmg.collections.DListImpl
#
# org.odmg.DArray implementation class
-DArrayClass=org.apache.ojb.odmg.collections.DListImpl_2
-#DArrayClass=org.apache.ojb.odmg.collections.DListImpl
+DArrayClass=org.apache.ojb.odmg.collections.DListImpl
#
# org.odmg.DMap implementation class
DMapClass=org.apache.ojb.odmg.collections.DMapImpl
1.13.2.2 +16 -80 db-ojb/src/test/org/apache/ojb/repository_internal.xml
Index: repository_internal.xml
===================================================================
RCS file: /home/cvs/db-ojb/src/test/org/apache/ojb/repository_internal.xml,v
retrieving revision 1.13.2.1
retrieving revision 1.13.2.2
diff -u -r1.13.2.1 -r1.13.2.2
--- repository_internal.xml 18 Sep 2004 13:06:40 -0000 1.13.2.1
+++ repository_internal.xml 3 Apr 2005 02:40:57 -0000 1.13.2.2
@@ -57,7 +57,7 @@
<!-- THIS IS THE OJB NAMED ROOTS TABLE, DO NOT EDIT-->
<class-descriptor
- class="org.apache.ojb.odmg.NamedRootsEntry"
+ class="org.apache.ojb.odmg.NamedRootsMap$NamedEntry"
table="OJB_NRM"
>
<field-descriptor
@@ -85,14 +85,13 @@
primarykey="true"
autoincrement="true"
/>
- <field-descriptor
- name="size"
- column="SIZE_"
- jdbc-type="INTEGER"
- />
+
<collection-descriptor
name="elements"
element-class-ref="org.apache.ojb.odmg.collections.DListEntry"
+ auto-retrieve = "true"
+ auto-update="none"
+ auto-delete="none"
>
<inverse-foreignkey field-ref="dlistId"/>
</collection-descriptor>
@@ -128,63 +127,6 @@
/>
</class-descriptor>
- <!-- THIS IS THE OJB DLIST IMPLEMENTATION, DO NOT EDIT-->
- <!-- alternative implementation of DList -->
- <class-descriptor
- class="org.apache.ojb.odmg.collections.DListImpl_2"
- table="OJB_DLIST"
- >
- <field-descriptor
- name="id"
- column="ID"
- jdbc-type="INTEGER"
- primarykey="true"
- autoincrement="true"
- />
- <field-descriptor
- name="size"
- column="SIZE_"
- jdbc-type="INTEGER"
- />
- <collection-descriptor
- name="elements"
- element-class-ref="org.apache.ojb.odmg.collections.DListEntry_2"
- auto-retrieve = "true"
- >
- <inverse-foreignkey field-ref="dlistId"/>
- </collection-descriptor>
- </class-descriptor>
-
-<!-- THIS IS THE OJB DLIST ENTRY IMPLEMENTATION, DO NOT EDIT-->
- <class-descriptor
- class="org.apache.ojb.odmg.collections.DListEntry_2"
- table="OJB_DLIST_ENTRIES"
- >
- <field-descriptor
- name="id"
- column="ID"
- jdbc-type="INTEGER"
- primarykey="true"
- autoincrement="true"
- />
- <field-descriptor
- name="dlistId"
- column="DLIST_ID"
- jdbc-type="INTEGER"
- />
- <field-descriptor
- name="position"
- column="POSITION_"
- jdbc-type="INTEGER"
- />
- <field-descriptor
- name="oid"
- column="OID_"
- jdbc-type="LONGVARBINARY"
- conversion="org.apache.ojb.broker.accesslayer.conversions.Object2ByteArrFieldConversion"
- />
- </class-descriptor>
-
<!-- THIS IS THE OJB DBAG IMPLEMENTATION, DO NOT EDIT-->
<class-descriptor
class="org.apache.ojb.odmg.collections.DBagImpl"
@@ -197,14 +139,12 @@
primarykey="true"
autoincrement="true"
/>
- <field-descriptor
- name="size"
- column="SIZE_"
- jdbc-type="INTEGER"
- />
<collection-descriptor
name="elements"
element-class-ref="org.apache.ojb.odmg.collections.DListEntry"
+ auto-retrieve = "true"
+ auto-update="none"
+ auto-delete="none"
>
<inverse-foreignkey field-ref="dlistId"/>
</collection-descriptor>
@@ -222,14 +162,12 @@
primarykey="true"
autoincrement="true"
/>
- <field-descriptor
- name="size"
- column="SIZE_"
- jdbc-type="INTEGER"
- />
<collection-descriptor
name="elements"
element-class-ref="org.apache.ojb.odmg.collections.DSetEntry"
+ auto-retrieve = "true"
+ auto-update="none"
+ auto-delete="none"
>
<inverse-foreignkey field-ref="dlistId"/>
</collection-descriptor>
@@ -277,15 +215,13 @@
primarykey="true"
autoincrement="true"
/>
- <field-descriptor
- name="size"
- column="SIZE_"
- jdbc-type="INTEGER"
- />
<collection-descriptor
name="entries"
element-class-ref="org.apache.ojb.odmg.collections.DMapEntry"
collection-class="org.apache.ojb.broker.util.collections.ManageableHashSet"
+ auto-retrieve = "true"
+ auto-update="none"
+ auto-delete="none"
>
<inverse-foreignkey field-ref="dmapId"/>
</collection-descriptor>
@@ -309,13 +245,13 @@
jdbc-type="INTEGER"
/>
<field-descriptor
- name="keyOID"
+ name="keyOid"
column="KEY_OID"
jdbc-type="LONGVARBINARY"
conversion="org.apache.ojb.broker.accesslayer.conversions.Object2ByteArrFieldConversion"
/>
<field-descriptor
- name="valueOID"
+ name="valueOid"
column="VALUE_OID"
jdbc-type="LONGVARBINARY"
conversion="org.apache.ojb.broker.accesslayer.conversions.Object2ByteArrFieldConversion"
No revision
No revision
1.54.2.40 +55 -1 db-ojb/release-notes.txt
Index: release-notes.txt
===================================================================
RCS file: /home/cvs/db-ojb/release-notes.txt,v
retrieving revision 1.54.2.39
retrieving revision 1.54.2.40
diff -u -r1.54.2.39 -r1.54.2.40
--- release-notes.txt 22 Mar 2005 18:15:53 -0000 1.54.2.39
+++ release-notes.txt 3 Apr 2005 02:40:57 -0000 1.54.2.40
@@ -8,6 +8,60 @@
relational databases. OJB provides ODMG and JDO interfaces.
---------------------------------------------------------------------
+Release 1.0.3
+---------------------------------------------------------------------
+NEW FEATURES:
+
+
+NOTES:
+- odmg-api: Named objects can now be non- and persistence capable objects. At least
+ the named object have to be serializable.
+
+CHANGES:
+- Refactoring DCollection implementations, remove DListImpl_2 classes (code moved to DListImpl)
+- Object2ByteArrFieldConversion: If source object on conversion javaToSQL is 'null', no longer create an
+ byte array simply return 'null'
+
+BUG FIXES:
+Please refer to our Bug tracking site (http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10700)
+to see details for a bug with id OJB-xxx.
+
+- odmg-api: OJB-7 - Fix critical property setting in OJB.properties file
+- odmg-api: OJB-8 - Fix bug when using cascading delete on empty 1:1 reference
+- odmg-api: Fix bug with named object. On 'unbind' of a named object, if the object is a persistence capable
+ object (object with metadata mapping), the object itself will not be deleted. All other (serializable)
+ named objects will be deleted on unbind.
+- odmg-api: Fix bug with named objects when using database based Identity columns (SequenceManagerNativeImpl)
+- odmg-api: Fix bug when persisting DCollection instances when using database based
+ Identity columns (SequenceManagerNativeImpl).
+
+
+
+KNOWN ISSUES:
+- Auto-Detection for insert/update objects checks to avoid DB queries the PK fields of the object.
+ If at least one PK field is 'NULL' or if primitive field '0', OJB assume the object is new and
+ needs insert. This will be configurable in next upcoming version. Workaround for PB-api: use method
+ PB#store(Object obj, ObjectModification mod) to state update or insert.
+- Batch handling doesn't work proper with optimistic locking. This will be fixed
+ in version 1.1
+- Subqueries are not extent aware. see QueryTest#testSubQueryAgainstExtents
+- When a class mapped on multiple joined tables was used in a reference only objects
+ of the base type class will be instantiated, e.g. a Company class has
+ 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)
+- 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.
+- Oracle9i platform: when using statement batching, there is a 2k limit on BLOB + 4k limit on CLOB.
+
+---------------------------------------------------------------------
Release 1.0.2
---------------------------------------------------------------------
NEW FEATURES:
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org