Author: chrish
Date: Tue Nov 10 14:52:15 2015
New Revision: 1713660
URL: http://svn.apache.org/viewvc?rev=1713660&view=rev
Log:
CMS commit to olingo by chrish
Modified:
olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext
Modified:
olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext
URL:
http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext?rev=1713660&r1=1713659&r2=1713660&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext
(original)
+++ olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext
Tue Nov 10 14:52:15 2015
@@ -75,7 +75,7 @@ The folling steps have to be performed:
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.
-Add the folling methods to the class `myservice.mynamespace.data.Storage`.
When a new transaction has been begun the data of the service is copied and
stored in an instance variable. If `rollbackTransaction` has been called the
current data is replaced with the previous copied one.
+Add the following methods to the class `myservice.mynamespace.data.Storage`.
When a new transaction has been begun the data of the service is copied and
stored in an instance variable. If `rollbackTransaction` has been called the
current data is replaced with the previous copied one.
::::java
private List<Entity> productListBeforeTransaction;
