[jbosscache-commits] JBoss Cache SVN: r4669 - in core/trunk/src/main: release and 1 other directory.

[jbosscache-commits at lists.jboss.org]

Author: mircea.markus
Date: 2007-10-23 07:06:11 -0400 (Tue, 23 Oct 2007)
New Revision: 4669

Modified:
   core/trunk/src/main/docbook/tutorial/en/master.xml
   core/trunk/src/main/release/build.xml
Log:
fixing

Modified: core/trunk/src/main/docbook/tutorial/en/master.xml
===================================================================
--- core/trunk/src/main/docbook/tutorial/en/master.xml	2007-10-23 09:06:30 UTC (rev 4668)
+++ core/trunk/src/main/docbook/tutorial/en/master.xml	2007-10-23 11:06:11 UTC (rev 4669)
@@ -95,12 +95,7 @@
 
       <para>The only script needed for this tutorial is the
          <literal>JBossCache/build.xml</literal>
-         ant script and the accompanying
-         driver scripts (
-         <literal>build.sh</literal>
-         for Unix and
-         <literal>build.bat</literal>
-         for Windows).
+         ant script. You also need to have <ulink url="http://ant.apache.org/">ant</ulink> installed for running the demo.
       </para>
    </section>
 
@@ -108,13 +103,11 @@
       <title>Running The Demo GUI</title>
 
       <para>
-         The demo is run by calling the ant script (via the driver) with the
-         <literal>run.demo</literal>
-         target. E.g.,
+         The demo is run by calling the ant script with the <literal>run.demo</literal> target. E.g.,
       </para>
 
       <para>
-         <literal>./build.sh run.demo</literal>
+         <literal>ant run.demo</literal>
       </para>
       <para>
          This will cause a GUI window to appear, giving you a tree view of the cache in the top pane and a BeanShell
@@ -154,8 +147,7 @@
    <section>
       <title>Tutorials</title>
       Note that it is recommended that you shut down and restart the demo GUI for each of the following tutorials, to
-      ensure
-      clean caches every time.
+      ensure clean caches every time.
       <section>
          <title>Caches and Nodes</title>
          <para>
@@ -285,6 +277,15 @@
             only starting transactions before creating/removing nodes or adding/removing data. This will depict how
             replication only occurs on transaction boundaries. Try rolling back a few transactions as well, to see how
             nothing gets replicated in these cases.
+            Below is the sample code for managing transactions:
+            <programlisting><![CDATA[
+
+              tm = cache.getTransactionManager();
+              tm.begin();
+              //do the operations here
+              tm.commit();//tm.rollback();
+              
+            ]]></programlisting>
          </para>
       </section>
 

Modified: core/trunk/src/main/release/build.xml
===================================================================
--- core/trunk/src/main/release/build.xml	2007-10-23 09:06:30 UTC (rev 4668)
+++ core/trunk/src/main/release/build.xml	2007-10-23 11:06:11 UTC (rev 4669)
@@ -141,6 +141,7 @@
          <classpath refid="test.classpath"/>
          <jvmarg value="${jvm.ipv4}"/>
          <jvmarg value="${jvm.localhost}"/>
+         <arg value="-console"/>
       </java>
    </target>