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 2002/11/28 23:36:32 UTC
cvs commit: jakarta-ojb/src/test/org/apache/ojb OJB.properties
arminw 2002/11/28 14:36:32
Modified: src/test/org/apache/ojb OJB.properties
Log:
adpat properties, change doc
Revision Changes Path
1.31 +31 -30 jakarta-ojb/src/test/org/apache/ojb/OJB.properties
Index: OJB.properties
===================================================================
RCS file: /home/cvs/jakarta-ojb/src/test/org/apache/ojb/OJB.properties,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- OJB.properties 27 Nov 2002 05:50:09 -0000 1.30
+++ OJB.properties 28 Nov 2002 22:36:32 -0000 1.31
@@ -60,7 +60,6 @@
# This is the singlevm implementation:
PersistenceBrokerClass=org.apache.ojb.broker.singlevm.PersistenceBrokerImpl
#
-#
#----------------------------------------------------------------------------------------
# PersistenceBrokerFactory pool
#----------------------------------------------------------------------------------------
@@ -107,19 +106,20 @@
# A ConnectionFactory is responsible for creating
# JDBC Connections. Current version ships three implementations:
#
-# 1. ConnectionFactoryDefaultImpl
-# No pooling, no playing around, be nice to your J2EE server.
+# 1. ConnectionFactoryNotPooledImpl
+# No pooling, no playing around.
# Every connection request returns a new connection,
-# every connection release close the connection. Use this implementation e.g if you
-# use Datasources from an application server.
-# 2. ConnectionFactoryConPooledImpl
-# This implementation support connection pooling.
-# 3. ConnectionFactoryStmtPooledImpl
-# This implementation support connection pooling and prepared statement pooling.
-# 4. ConnectionFactoryPassThroughImpl
-# Same as ConnectionFactoryDefaultImpl, but every con.commit() call within OJB
-# was ignored by the connection. Use this implementation e.g if you
-# use Datasources from an application server.
+# every connection release close the connection.
+# 2. ConnectionFactoryPooledImpl
+# This implementation supports connection pooling.
+# 3. ConnectionFactoryDBCPImpl
+# Using the jakarta-DBCP api for connection management, support
+# connection- and prepared statement-pooling.
+# 4. ConnectionFactoryManagedImpl
+# Connection factory for use within managed environments - e.g. JBoss.
+# Every obtained DataSource was wrapped within OJB (and ignore
+# e.g. con.commit() calls within OJB).
+# Use this implementation e.g if you use Datasources from an application server.
#
# Use the OJB performance tests to decide, which implementation is best for you.
# The proper way of obtaining a connection is configured in
@@ -128,10 +128,10 @@
# take a look at the repository.dtd, there was a possibility to override
# this default connection factory entry in each JDBCConnectionDescriptor.
#
-#ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryDefaultImpl
-ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryConPooledImpl
-#ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryStmtPooledImpl
-#ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryPassThroughImpl
+ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryPooledImpl
+#ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryNotPooledImpl
+#ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryManagedImpl
+#ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryDBCPImpl
#
# Specifies maximum number of connections that can be borrowed from a
# connection pool at one time. When non-positive, there is no limit.
@@ -152,7 +152,6 @@
# if true, exceptions caused by setting autocommit state, will be ignored
ignoreAutoCommitExceptions=false
#
-#
#----------------------------------------------------------------------------------------
# SqlGenerator
#----------------------------------------------------------------------------------------
@@ -168,18 +167,21 @@
# The SequenceManagerClass entry determines the SequenceManager to be used
# choose one of the implementations:
#----------------------------------
-# H/L sequence manager implementation
-SequenceManagerClass=org.apache.ojb.broker.util.sequence.SequenceManagerHiLoImpl
+# 1. SequenceManagerHiLoImpl
+# High/Low sequence manager implementation
+# 2. SequenceManagerHiLoContinuousImpl
+# High/Low sequence manager implementation
+# generates continuous id's during runtime
+# 3. SequenceManagerInMemoryImpl
+# InMemory-sequence manager generates continuous id's during runtime
+# This is the fastest standard sequence manager implementation, but
+# has some Limitations:
+# - do not use in client/server mode
+# - do not use in clustered environments
+# - do not use if other entities generate id's for objects
#
-# H/L sequence manager generates continuous id's during runtime
+SequenceManagerClass=org.apache.ojb.broker.util.sequence.SequenceManagerHiLoImpl
#SequenceManagerClass=org.apache.ojb.broker.util.sequence.SequenceManagerHiLoContinuousImpl
-#
-# InMemory-sequence manager generates continuous id's during runtime
-# This is the fastest standard sequence manager implementation, but
-# has some Limitations:
-# do not use in client/server mode
-# do not use in clustered environments
-# do not use if other entities generate id's for objects
#SequenceManagerClass=org.apache.ojb.broker.util.sequence.SequenceManagerInMemoryImpl
#-----------------------------------
#
@@ -200,8 +202,7 @@
#
# Here you can induce the sequence manager to use a
# different as the default repository to generate sequences
-# (if using org.apache.ojb.broker.util.sequence.SequenceManagerHiLoImpl
-# or org.apache.ojb.broker.util.sequence.SequenceManagerHiLoContinuousImpl).
+# (if using one of the standard sequence manager implementations).
# The used class descriptor could be
# found under 'org.apache.ojb.broker.util.sequence.HighLowSequence' in
# repository_internal.xml.