Author: chrish
Date: Tue Nov 10 15:03:04 2015
New Revision: 1713663
URL: http://svn.apache.org/viewvc?rev=1713663&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=1713663&r1=1713662&r2=1713663&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 15:03:04 2015
@@ -281,7 +281,7 @@ After building and deploying your servic
All requests are issued againest
[http://localhost:8080/DemoService-Action/DemoService.svc/$batch](http://localhost:8080/DemoService-Action/DemoService.svc/$batch)
Set the Content-Type header to `Content-Type: multipart/mixed;boundary=abc123`
-**Example 1**
+**Example 1**
Please note that the second request in the Change Set references the first
request of the Change Set.
This is done by by prefixing the Content-Id of the referenced request with a
$. e.g. `$abc`
@@ -341,7 +341,7 @@ Now have a look at the response. As you
]
}
-**Example 2**
+**Example 2**
Let us try what is happing if the send a invalid request within a Change Set.
Use the same URI and Content Type as before and use the folling body:
--abc123
