svn commit: r971991 - in /websites/staging/olingo/trunk/content: ./ doc/odata4/tutorials/batch/tutorial_batch.html

[bu...@apache.org]

Author: buildbot
Date: Tue Nov 10 14:51:14 2015
New Revision: 971991

Log:
Staging update by buildbot for olingo

Modified:
    websites/staging/olingo/trunk/content/   (props changed)
    websites/staging/olingo/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.html

Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 10 14:51:14 2015
@@ -1 +1 @@
-1713654
+1713658

Modified: websites/staging/olingo/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.html (original)
+++ websites/staging/olingo/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.html Tue Nov 10 14:51:14 2015
@@ -127,9 +127,11 @@ Each part of a Multipart MINE message ca
 <h1 id="2-implementation">2. Implementation<a class="headerlink" href="#2-implementation" title="Permanent link">&para;</a></h1>
 <p>The main idea of the following implementation is to reuse the existing processors.
 To do so, we will implement a new processor, which takes a batch request and dispatches the single requests to the responsible processors.</p>
-<p>The folling steps have to be performed:
- * Modify the data store
- * Implement the interface <code>BatchProcessor</code></p>
+<p>The folling steps have to be performed:</p>
+<ul>
+<li>Modify the data store</li>
+<li>Implement the interface <code>BatchProcessor</code></li>
+</ul>
 <h2 id="add-transactional-behaviour-to-the-data-store">Add transactional behaviour to the data store<a class="headerlink" href="#add-transactional-behaviour-to-the-data-store" title="Permanent link">&para;</a></h2>
 <p>Before we start with the actual processor implementation the data store has to be modified to provide transactional behavior. In real world service the underlaying database may supports transactional handling. This tutorial is not based on a database so we have implement a simple transaction handling by ourself.</p>
 <p>Add the folling methods to the class <code>myservice.mynamespace.data.Storage</code>. When a new transaction has been begun the data of the service is copied and stored in an instance variable. If <code>rollbackTransaction</code> has been called the current data is replaced with the previous copied one.</p>