svn commit: r1677580 - /olingo/site/trunk/content/doc/odata4/tutorials/read/tutorial_read.mdtext

[mibo]

Author: mibo
Date: Mon May  4 11:16:40 2015
New Revision: 1677580

URL: http://svn.apache.org/r1677580
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=1677580&r1=1677579&r2=1677580&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 
Mon May  4 11:16:40 2015
@@ -322,7 +322,7 @@ As we can see, the Olingo server API pro
 
 Some of these interfaces are going to be used in the following sections.
 Note:
-You can find the Javadoc here: 
http://olingo.apache.org/javadoc/odata4/index.html
+You can find the Javadoc here: 
<http://olingo.apache.org/javadoc/odata4/index.html>
 
 
 ### 4.1.3. Implement the required methods
@@ -817,11 +817,11 @@ Create Java class with name _DemoServlet
 
 ![createJavaServletClass](createJavaServletClass.png "Creating the servlet 
class")
 
-Override the _service()_ method.  
+Override the `service()` method.  
 Basically, what we’re doing here is to create an _ODataHttpHandler_, which 
is a class that is provided by _Olingo_.
 It receives the user request and if the URL conforms to the OData 
specification, the request is delegated to the processor implementation of the 
OData service.
 This means that the handler has to be configured with all processor 
implementations that have been created along with the OData service (in our 
example, only one processor).
-Furthermore, the _ODataHttpHandler_ needs to carry the knowledge about the 
_EdmProvider_.
+Furthermore, the `ODataHttpHandler` needs to carry the knowledge about the 
`EdmProvider`.
 
 As such, here’s the location where our 2 implemented classes come together, 
the metadata declaration and the data provisioning.
 
@@ -1009,10 +1009,10 @@ Our first OData service is very simple;
 **Outlook**
 
 Further topics to be covered by follow-up tutorials:  
-* READ scenario: reading single entity, reading property  
-* WRITE scenario: executing PUT, POST and DELETE requests  
-* Navigation: navigating from one entity to a corresponding second entity
-* Data types
+  * READ scenario: reading single entity, reading property  
+  * WRITE scenario: executing PUT, POST and DELETE requests  
+  * Navigation: navigating from one entity to a corresponding second entity
+  * Data types
 
 
 **Further reading**