Author: chrish
Date: Tue Oct 20 00:42:38 2015
New Revision: 1709495
URL: http://svn.apache.org/viewvc?rev=1709495&view=rev
Log:
CMS commit to olingo by chrish
Modified:
olingo/site/trunk/content/doc/odata4/tutorials/media/tutorial_media.mdtext
Modified:
olingo/site/trunk/content/doc/odata4/tutorials/media/tutorial_media.mdtext
URL:
http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata4/tutorials/media/tutorial_media.mdtext?rev=1709495&r1=1709494&r2=1709495&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata4/tutorials/media/tutorial_media.mdtext
(original)
+++ olingo/site/trunk/content/doc/odata4/tutorials/media/tutorial_media.mdtext
Tue Oct 20 00:42:38 2015
@@ -365,7 +365,7 @@ To keep things simple, our scenario do n
}
}
-Updating a media entity in our scenario is quite similar to read an entity.
The first step is to analyse the URI, than fetch the entity from data store.
Afer that we call the `updateMediaEntity` method. In our case we do not return
any content. If we would return content, we must return the recently uploaded
content of the media entity.
+Updating a media entity in our scenario is quite similar to read an entity.
The first step is to analyse the URI, than fetch the entity from data store.
Afer that we call the `updateMediaEntity` method. In our case we do not return
any content. If we would return content, we must return the recently uploaded
content of the media entity ([OData Version 4.0 Part 1:
Protocol](http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html#_Toc406398338)).
:::java
@Override
