Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Date: 19 Mar 2005 10:37:50 -0000
Message-ID: <20050319103750.55920.qmail@minotaur.apache.org>
From: arminw@apache.org
To: db-ojb-cvs@apache.org
Subject: cvs commit: db-ojb/src/test/org/apache/ojb OJB.properties

arminw      2005/03/19 02:37:50

  Modified:    src/test/org/apache/ojb Tag: OJB_1_0_RELEASE OJB.properties
  Log:
  rearrange properties
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.75.2.4  +27 -27    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.3
  retrieving revision 1.75.2.4
  diff -u -r1.75.2.3 -r1.75.2.4
  --- OJB.properties	18 Mar 2005 19:22:31 -0000	1.75.2.3
  +++ OJB.properties	19 Mar 2005 10:37:50 -0000	1.75.2.4
  @@ -256,24 +256,6 @@
   # that a lock may be hold. Defaults to 60000 = 1 minute
   LockTimeout=60000
   #
  -# 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.
  -# 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 and there is also no recursive locking.
  -ImplicitLocking=true
  -#ImplicitLocking=false
  -#
  -# The LockAssociations entry defines the behaviour for the OJB
  -# 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.
  -#LockAssociations=READ
  -LockAssociations=WRITE
   #
   # ------ deprecated ------
   # The LockMapClass entry tells OJB which concrete LockMap
  @@ -316,7 +298,7 @@
   #
   #
   #----------------------------------------------------------------------------------------
  -# ODMG settings
  +# ODMG-api settings
   #----------------------------------------------------------------------------------------
   # Specify the used base class for ODMG API
   # - ImplementationDefaultImpl is the default class
  @@ -326,6 +308,14 @@
   ImplementationClass=org.apache.ojb.odmg.ImplementationImpl
   #ImplementationClass=org.apache.ojb.odmg.ImplementationJTAImpl
   #
  +# Specify the used tx handling.
  +# - LocalTxManager use if you want the transaction to be associated by a thread
  +# - JTATxManager use if you want the transaction to be associated via the Transaction
  +# manager that is in your application server.
  +#
  +OJBTxManagerClass=org.apache.ojb.odmg.LocalTxManager
  +#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
  @@ -342,14 +332,24 @@
   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
  +# 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.
  +ImplicitLocking=true
  +#ImplicitLocking=false
   #
  -# Specify the used tx handling.
  -# - LocalTxManager use if you want the transaction to be associated by a thread
  -# - JTATxManager use if you want the transaction to be associated via the Transaction
  -# manager that is in your application server.
  -#
  -OJBTxManagerClass=org.apache.ojb.odmg.LocalTxManager
  -#OJBTxManagerClass=org.apache.ojb.odmg.JTATxManager
  +# The LockAssociations entry defines the behaviour for the OJB
  +# 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.
  +#LockAssociations=READ
  +LockAssociations=WRITE
   #
   #
   # 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