arminw 2005/06/04 07:49:53
Modified: src/test/org/apache/ojb Tag: OJB_1_0_RELEASE OJB.properties
. Tag: OJB_1_0_RELEASE release-notes.txt
Log:
update release-notes
add new odmg-extensions/properties:
- 'ordering' Allow to dis-/enable OJB's object ordering on transaction commit
- 'noteUserOrder' If true the order of persisting/locking method calls
determine the order of objects before commit.
- 'implicitLocking' Dis-/enable OJB's implicit locking
- introduce new object state 'StateTransient' for deleted, not persistent
objects
Revision Changes Path
No revision
No revision
1.75.2.8 +35 -21 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.7
retrieving revision 1.75.2.8
diff -u -r1.75.2.7 -r1.75.2.8
--- OJB.properties 3 Apr 2005 02:40:57 -0000 1.75.2.7
+++ OJB.properties 4 Jun 2005 14:49:52 -0000 1.75.2.8
@@ -317,28 +317,14 @@
#OJBTxManagerClass=org.apache.ojb.odmg.JTATxManager
#
#
-# Specify the cascading delete behavior of the odmg-api. The
-# specified settings will be used by odmg-api as default settings. It
-# is also possible to change these settings at runtime using the
-# TransactionExt#setCascadingDelete method.
-#
-# Enable disable cascading delete for 1:1 references
-cascadingDeleteOneToOne=false
-#
-# Enable disable cascading delete for 1:n references
-cascadingDeleteOneToN=false
-#
-# Enable disable cascading delete for m:n references
-cascadingDeleteMToN=false
-#
-#
# The ImplicitLocking entry defines if implicit lock acquisition is
-# to be used. If set to 'true' OJB implicitely locks objects to ODMG
-# transactions after performing OQL queries and lookup objects.
-# If implicit locking is used locking objects is recursive, that is
+# to be used. If set to 'true' OJB implicitly locks objects to ODMG
+# transactions after performing OQL queries.
+# Also if implicit locking is used locking objects is recursive, that is
# associated objects are also locked.
# If ImplicitLocking is set to 'false', no locks are obtained in OQL
# queries, lookup objects and there is also no recursive locking.
+# This setting can be changed at runtime using OJB's ODMG extensions.
ImplicitLocking=true
#ImplicitLocking=false
#
@@ -346,11 +332,31 @@
# implicit locking feature. If set to WRITE (default) acquiring a write-
# lock on a given object x implies write locks on all objects associated
# to x. If set to READ implicit read-locks are acquired.
-# Acquiring a read-lock on x thus allways results in implicit read-locks
-# on all associated objects.
+# Acquiring a read-lock on x allways results in implicit read-locks
+# on all associated objects (if 'implicit locking' is enabled).
+# This setting can be changed at runtime using OJB's ODMG extensions.
#LockAssociations=READ
LockAssociations=WRITE
#
+# Enable/Disable OJB's persistent object ordering algorithm on commit
+# of a transaction. If enabled OJB try to calculate a valid order for
+# all new/modified objects (and referenced objects).
+# If the used databases support 'deferred checks' it's recommended to use
this
+# feature and to disable OJB's object ordering.
+# This setting can be changed at runtime using OJB's ODMG extensions.
+Ordering=true
+#
+# Allows to influence the order of objects (used when the transaction
commits).
+# If 'true' method calls like
+# - org.odmg.Transaction#lock(Object, int)
+# - org.odmg.Database#deletePersistent(Object)
+# - org.odmg.Database#makePersistent(Object)
+# determine the order of objects before commit.
+# Note: If OJB's ordering is enabled the order of objects may change
+# at commit of the transaction.
+# This setting can be changed at runtime using OJB's ODMG extensions.
+NoteUserOrder=true
+#
#
# Used ODMG collection implementation classes
# (e.g. when do a Implementation#newDlist() call)
@@ -371,6 +377,14 @@
DSetClass=org.apache.ojb.odmg.collections.DSetImpl
#
#
+# @deprecated property for backward compatibility.
+# If set 'true' the behavior of method
+# ImplementationImpl#setImplicitLocking(...) will be the same as
+# in OJB <=1.0.3 and disable the new possibility of global 'implicit locking'
+# setting at runtime with ImplementationExt#setImplicitLocking.
+# This is only for backward compatibility and will
+# be removed at a later date.
+ImplicitLockingBackward=false
#----------------------------------------------------------------------------------------
# Meta data / mapping settings
#----------------------------------------------------------------------------------------
No revision
No revision
1.54.2.47 +19 -3 db-ojb/release-notes.txt
Index: release-notes.txt
===================================================================
RCS file: /home/cvs/db-ojb/release-notes.txt,v
retrieving revision 1.54.2.46
retrieving revision 1.54.2.47
diff -u -r1.54.2.46 -r1.54.2.47
--- release-notes.txt 26 Apr 2005 22:03:18 -0000 1.54.2.46
+++ release-notes.txt 4 Jun 2005 14:49:53 -0000 1.54.2.47
@@ -20,7 +20,15 @@
NEW FEATURES:
* [OJB-31] - Configurable JDBC driver-setting setFetchSize
* [OJB-14] - Setting custom JDBC driver tuning options trough
jdbc-connection-descriptor
-* [OJB-6] - Support for stored procedures returning ResultSet.
+* [OJB-6] - Support for stored procedures returning ResultSet.
+* [OJB-41] - ODMG-api: Allow cascading delete using auto-delete setting in
metadata
+* Add new ODMG extensions and configuration properties. All properties can
be set
+ as global property in class ImplementationExt and for a specific
transaction in
+ class TransactionExt:
+ - 'ordering' Allow to dis-/enable OJB's object ordering on transaction
commit
+ - 'noteUserOrder' If true the order of persisting/locking method calls
+ determine the order of objects before commit.
+ - 'implicitLocking' Dis-/enable OJB's implicit locking
NOTES:
* Internal OJB class configuration files are changed, don't forget to replace
@@ -30,8 +38,14 @@
Now the tests more fair for registered API's
CHANGES:
+* Pluggable class interfaces changed to support OJB-31 and OJB-6:
+ StatementsForClassIF, StatementManagerIF, Platform
* Removed deprecated SequenceManager implementation SequenceManagerMySQLImpl
-* Remove unused method from SequenceManager interface
+* Remove unused method #setReferenceFKs from SequenceManager interface
+* ODMG-api: Method behavior of
ImplementationImpl#setImplicitLocking(boolean) changed.
+ Now this method set the global property for 'implicitLocking'. Old version
only changed the
+ implicit locking behavior for the current used transaction, this is moved
to
+ TransactionExt#setImplicitLocking
* Internal used OJB_HL_SEQ table changed. Remove of deprecated column.
If the SequenceManagerHighLowImpl was used and problems occur after
upgrade, please
drop and recreate this table without removed column
@@ -67,6 +81,8 @@
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.3
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
