db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From arm...@apache.org
Subject svn commit: r474570 - /db/ojb/branches/OJB_1_0_RELEASE/src/test/org/apache/ojb/OJB.properties
Date Mon, 13 Nov 2006 23:27:57 GMT
Author: arminw
Date: Mon Nov 13 15:27:56 2006
New Revision: 474570

URL: http://svn.apache.org/viewvc?view=rev&rev=474570
Log:
add new odmg-api property

Modified:
    db/ojb/branches/OJB_1_0_RELEASE/src/test/org/apache/ojb/OJB.properties

Modified: db/ojb/branches/OJB_1_0_RELEASE/src/test/org/apache/ojb/OJB.properties
URL: http://svn.apache.org/viewvc/db/ojb/branches/OJB_1_0_RELEASE/src/test/org/apache/ojb/OJB.properties?view=diff&rev=474570&r1=474569&r2=474570
==============================================================================
--- db/ojb/branches/OJB_1_0_RELEASE/src/test/org/apache/ojb/OJB.properties (original)
+++ db/ojb/branches/OJB_1_0_RELEASE/src/test/org/apache/ojb/OJB.properties Mon Nov 13 15:27:56
2006
@@ -43,7 +43,7 @@
 # found a error is logged. This can help to avoid store/delete calls without a running
 # PB-tx while development. Default setting is 'false'. (Note: When using OJB in a managed
 # environment *without* OJB-caching, it's valid to use store/delete calls without a running
-# PB-tx if the used PB instance was immediately closed after use)
+# PB-tx - if the used PB instance is immediately closed after use)
 TxCheck=false
 #
 # This setting can be helpful during development to detect PersistenceBroker leaks
@@ -263,37 +263,6 @@
 #
 #
 #----------------------------------------------------------------------------------------
-# ManageableCollection default settings
-#----------------------------------------------------------------------------------------
-# OJB use specific collection class implementations to provide 1:n and m:n references.
-# It's also possible to define specific collection classes for each defined 1:n or m:n
-# reference - please see documentation (repository mapping docs).
-#
-# Default collection classes for 1:n references
-CollectionTypes.OneToManyArray=org.apache.ojb.broker.util.collections.RemovalAwareCollection
-CollectionTypes.OneToManyCollection=org.apache.ojb.broker.util.collections.RemovalAwareCollection
-CollectionTypes.OneToManyList=org.apache.ojb.broker.util.collections.RemovalAwareList
-CollectionTypes.OneToManyVector=org.apache.ojb.broker.util.collections.RemovalAwareVector
-CollectionTypes.OneToManySet=org.apache.ojb.broker.util.collections.RemovalAwareSet
-#
-# Default collection classes for m:n references (never use a removal aware collection
-# implementation for m:n relation)
-CollectionTypes.ManyToManyArray=org.apache.ojb.broker.util.collections.ManageableArrayList
-CollectionTypes.ManyToManyCollection=org.apache.ojb.broker.util.collections.ManageableArrayList
-CollectionTypes.ManyToManyList=org.apache.ojb.broker.util.collections.ManageableArrayList
-CollectionTypes.ManyToManyVector=org.apache.ojb.broker.util.collections.ManageableVector
-CollectionTypes.ManyToManySet=org.apache.ojb.broker.util.collections.ManageableHashSet
-#
-# The Query/OQLQuery entries define the collection types returned
-# from Criteria-based queries/OQL-queries. By default this value is set to a List.
-# This will be good for most situations. If you need the additional features replace
-# the implementation.
-# Default collection classes query results
-CollectionTypes.Query=org.apache.ojb.broker.util.collections.ManageableArrayList
-CollectionTypes.OQLQuery=org.apache.ojb.broker.util.collections.ManageableArrayList
-#
-#
-#----------------------------------------------------------------------------------------
 # Meta data / mapping settings
 #----------------------------------------------------------------------------------------
 # The PersistentFieldClass property defines the implementation class
@@ -372,6 +341,37 @@
 #
 #
 #----------------------------------------------------------------------------------------
+# ManageableCollection default settings
+#----------------------------------------------------------------------------------------
+# OJB use specific collection class implementations to provide 1:n and m:n references.
+# It's also possible to define specific collection classes for each defined 1:n or m:n
+# reference - please see documentation (repository mapping docs).
+#
+# Default collection classes for 1:n references
+CollectionTypes.OneToManyArray=org.apache.ojb.broker.util.collections.RemovalAwareCollection
+CollectionTypes.OneToManyCollection=org.apache.ojb.broker.util.collections.RemovalAwareCollection
+CollectionTypes.OneToManyList=org.apache.ojb.broker.util.collections.RemovalAwareList
+CollectionTypes.OneToManyVector=org.apache.ojb.broker.util.collections.RemovalAwareVector
+CollectionTypes.OneToManySet=org.apache.ojb.broker.util.collections.RemovalAwareSet
+#
+# Default collection classes for m:n references (never use a removal aware collection
+# implementation for m:n relation)
+CollectionTypes.ManyToManyArray=org.apache.ojb.broker.util.collections.ManageableArrayList
+CollectionTypes.ManyToManyCollection=org.apache.ojb.broker.util.collections.ManageableArrayList
+CollectionTypes.ManyToManyList=org.apache.ojb.broker.util.collections.ManageableArrayList
+CollectionTypes.ManyToManyVector=org.apache.ojb.broker.util.collections.ManageableVector
+CollectionTypes.ManyToManySet=org.apache.ojb.broker.util.collections.ManageableHashSet
+#
+# The Query/OQLQuery entries define the collection types returned
+# from Criteria-based queries/OQL-queries. By default this value is set to a List.
+# This will be good for most situations. If you need the additional features replace
+# the implementation.
+# Default collection classes query results
+CollectionTypes.Query=org.apache.ojb.broker.util.collections.ManageableArrayList
+CollectionTypes.OQLQuery=org.apache.ojb.broker.util.collections.ManageableArrayList
+#
+#
+#----------------------------------------------------------------------------------------
 # repository file settings
 #----------------------------------------------------------------------------------------
 # The repositoryFile entry tells OJB to use this file as as its standard mapping
@@ -389,7 +389,6 @@
 # If Repository serialization is used the entry serializedRepositoryPath defines the
 # directory where the Repository is written to and read from.
 # this entry is used only when the useSerializedRepository flag is set to true
-#
 serializedRepositoryPath=.
 #
 #
@@ -516,6 +515,27 @@
 # feature and to disable OJB's object ordering.
 # This setting can be changed at runtime using OJB's ODMG extensions.
 Ordering=true
+#
+# If set 'true' an optimized and performant way is used to detect the
+# state (persistent/transient) of an object.
+# The detection of transient objects could be costly (e.g. if a
+# select of ID in database is used to check if object already
+# exists) we do:
+# a.
+# Check if the object Identity mark the specified object as transient.
+# If this is 'false' the object has populated primary key fields,
+# if 'true' at least one PK field is <em>null</em>
+# and the object is transient.
+# b.
+# Then we check if the object was already registered in current transaction.
+# if 'true' we can ask for transient state.
+# c.
+# If the primary key fields are defined/mapped as 'autoIncrement' fields and
+# 'optimizedTransientObjectDetection' is enabled OJB assume that the object
+# is persistent. If the PK fields are not 'autoIncrement' fields or the
+# optimized detection is disabled a database "exists object"-query is
+# performed to check if the object is persistent or transient.
+OptimizedTransientObjectDetection=true
 #
 #
 # Used ODMG collection implementation classes



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