User: gropi
Date: 01/06/01 23:35:11
Modified: src/docs advconfig.xml
Log:
Update on Option D by Georg Rehfeld
Revision Changes Path
1.11 +5 -5 manual/src/docs/advconfig.xml
Index: advconfig.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/docs/advconfig.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- advconfig.xml 2001/05/28 13:49:56 1.10
+++ advconfig.xml 2001/06/02 06:35:11 1.11
@@ -471,7 +471,7 @@
</listitem>
<listitem>
<para>
-<![CDATA[<commit-option> must be A, B, C, D (after 2.2.1). ]]></para>
+<![CDATA[<commit-option> must be A, B, C, D (in CVS version). ]]></para>
<para>
Option A: The container caches the beans state between transactions.
This options assumes that the bean/container is the only one accessing
@@ -501,13 +501,13 @@
invalid and might already have changed in the persistent storage when
the business method executes.</para>
<para>
-Option D: This is a JBoss specific feature available in versions
-newer than the 2.2.1 release. It enables a lazy read schema, where
+Option D: This is a JBoss specific feature available in the actual
+version from CVS only. It enables a lazy read schema, where
the beans state is cached between transactions as with option A,
but resynchronized from the persistent storage from time to time
-(via ejbLoad). The default time between resynchronizations is 5
+(via ejbLoad). The default time between resynchronizations is 30
seconds but you may configure the time (in seconds) with
-<![CDATA[<optiond-refresh-rate>30</optiond-refresh-rate>]]>.</para>
+<![CDATA[<optiond-refresh-rate>42</optiond-refresh-rate>]]>.</para>
<para>
With all four commit options the container must synchronize the
bean instances cached state with the persistent storage (via ejbStore)
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
