Author: mibo
Date: Tue Apr 28 12:50:49 2015
New Revision: 1676521
URL: http://svn.apache.org/r1676521
Log:
CMS commit to olingo by mibo
Modified:
olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext
Modified:
olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext
URL:
http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext?rev=1676521&r1=1676520&r2=1676521&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext
(original)
+++ olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext
Tue Apr 28 12:50:49 2015
@@ -710,12 +710,13 @@ The steps for implementating the method
1. Which data is requested?
Usually, an OData service provides different _EntitySets_, so first it is
required to identify which _EntitySet_ has been requested. This information can
be retrieved from the _uriInfo_ object
+
2. Fetch the data
As a developer of the OData service, you have to know how and where the data
is stored. In many cases, this would be a database. At this point, you would
connect to your database and fetch the requested data with an appropriate SQL
statement. The data that is fetched from the data storage has to be put into an
_EntitySet_ object.
Note that this object has to be of type _EntitySet_, not _EdmEntitySet_
The package _org.apache.olingo.commons.api.data_ provides interfaces that
describe the actual data, not the metadata.
-
+ 
3. Transform the data
_Olingo_ expects from us to provide the data as low-level _InputStream_
object. However, _Olingo_ supports us in doing so, by providing us with a
proper "serializer".
@@ -756,7 +757,7 @@ The steps for implementating the method
response.setContent(serializedContent);
response.setStatusCode(HttpStatusCode.OK.getStatusCode());
response.setHeader(HttpHeader.CONTENT_TYPE,
responseFormat.toContentTypeString());
- }
+ }
**_getData()_**
