arminw 2005/08/08 10:06:30
Modified: src/doc/forrest/src/documentation/content/xdocs/docu/guides
Tag: OJB_1_0_RELEASE repository.xml
src/test/org/apache/ojb Tag: OJB_1_0_RELEASE repository.dtd
Log:
update, clarify docs
Revision Changes Path
No revision
No revision
1.1.2.9 +21 -13
db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/repository.xml
Index: repository.xml
===================================================================
RCS file:
/home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/repository.xml,v
retrieving revision 1.1.2.8
retrieving revision 1.1.2.9
diff -u -r1.1.2.8 -r1.1.2.9
--- repository.xml 30 Apr 2005 19:38:09 -0000 1.1.2.8
+++ repository.xml 8 Aug 2005 17:06:29 -0000 1.1.2.9
@@ -379,15 +379,23 @@
application server).
</li>
<li>
- 1 - Set autoCommit explicitly to
- <em>true</em>
- when a connection is created, and temporary
set to
- <em>false</em> when necessary (default mode).
+ 1 - [default mode] set the connection's
<em>autoCommit</em> state temporary to
+ 'false' if needed (when using transaction
demarcation in non-managed environment)
+ and restore the 'old' state after use.
+ <br/>
+ In versions before <em>OJB 1.0.4</em> the
autoCommit state was
+ explicit set 'true' when connection was
created, now OJB expect that
+ this is done by the jdbc-driver/DataSource
configuration. To enable the old
+ behavior set a <link
href="#custom-attribute">custom attribute</link>
+ <em>initializationCheck</em> to 'true'.
+ <source><![CDATA[
+ <attribute attribute-name="initializationCheck" attribute-value="false"
/>]]></source>
+ Then OJB set the <em>autoCommit</em> state
explicitly to 'true' when
+ the connection is created by the <link
href="site:connection">ConnectionFactory</link>.
</li>
<li>
- 2 - Set autoCommit explicitly to
- <em>false</em>
- when a connection is created.
+ 2 - Set the connection's <em>autoCommit</em>
explicitly to
+ <em>false</em> when a connection is created.
</li>
</ul>
</section>
@@ -769,7 +777,8 @@
<title>object-cache</title>
<p>
The
- <em>object-cache</em> element can be used to specify the
ObjectCache
+ <em>object-cache</em> element can be used to specify the
+ <link href="site:object-cache">ObjectCache</link>
implementation used by OJB. There are three levels of
declaration:
</p>
<ul>
@@ -859,8 +868,7 @@
/>
...
<attribute attribute-name="myAttribute" attribute-value="myValue"/>
-</class-descriptor>
- ]]></source>
+</class-descriptor>]]></source>
<p>
To access the attribute you have to know the associated
<code>AttributeContainer</code>
class. Here it was <link
href="ext:api/class-descriptor">ClassDescriptor</link>. To read
@@ -960,8 +968,8 @@
to materialize instances of the persistent class.
</p>
<p>
- The
- <em>extends</em> attribute ************TODO:
description*************
+ The <em>extends</em> attribute is
<strong>deprecated</strong> and will be removed
+ or reintroduced with changed funcitonality in future.
DON'T USE IT!
</p>
<p>
The <em>accept-locks</em> attribute specifies whether
implicit locking should propagate to this class.
No revision
No revision
1.56.2.7 +11 -5 db-ojb/src/test/org/apache/ojb/repository.dtd
Index: repository.dtd
===================================================================
RCS file: /home/cvs/db-ojb/src/test/org/apache/ojb/repository.dtd,v
retrieving revision 1.56.2.6
retrieving revision 1.56.2.7
diff -u -r1.56.2.6 -r1.56.2.7
--- repository.dtd 30 Apr 2005 20:55:15 -0000 1.56.2.6
+++ repository.dtd 8 Aug 2005 17:06:30 -0000 1.56.2.7
@@ -116,15 +116,18 @@
The useAutoCommit attribute allow to set how OJB uses
the autoCommit state of the used connections. The default mode
- was 1. When using mode 0 or 2 with the PB-api, you must use PB
- transaction demarcation.
+ was 1.
0 - OJB ignores the autoCommit setting of the connection and do not
try to change it. This mode could be helpfully if the
connection don't let you set the autoCommit state
(e.g. using datasources from application server).
- 1 - set autoCommit explicit 'true' when connection was created
- and temporary set to 'false' when necessary (default mode).
- 2 - set autoCommit explicit 'false' when connection was created.
+ 1 - [default mode] set the connection's autoCommit state temporary to
'false' if needed
+ (when using transaction) and restore the old state after use. In
+ versions before OJB 1.0.4 the autoCommit state was explicit set
'true'
+ when connection was created, now OJB expect that this was done by
+ the jdbc-driver configuration. To enable old behavior set a custom
attribute
+ 'initializationCheck' to 'true'.
+ 2 - this setting set autoCommit explicit 'false' when connection was
created.
If the ignoreAutoCommitExceptions attribute is set 'true', all
exceptions caused by setting autocommit state, will be ignored.
@@ -455,6 +458,9 @@
This class will be used as the RowReader implementation used to
materialize instances of the persistent class.
+ The extends attribute is deprecated and will be removed or reintroduced
+ with changed funcitonality in future. DON'T USE IT!
+
The accept-locks attribute specifies whether implicit locking should
propagate to this class. Currently relevant for the ODMG layer only.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
