Author: buildbot
Date: Mon May 4 11:16:54 2015
New Revision: 950039
Log:
Staging update by buildbot for olingo
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/doc/odata4/tutorials/read/tutorial_read.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon May 4 11:16:54 2015
@@ -1 +1 @@
-1677010
+1677580
Modified:
websites/staging/olingo/trunk/content/doc/odata4/tutorials/read/tutorial_read.html
==============================================================================
---
websites/staging/olingo/trunk/content/doc/odata4/tutorials/read/tutorial_read.html
(original)
+++
websites/staging/olingo/trunk/content/doc/odata4/tutorials/read/tutorial_read.html
Mon May 4 11:16:54 2015
@@ -328,7 +328,7 @@ Accordingly, we understand that the <em>
<p><img alt="edmPackage" src="edmPackage.png" title="The edm package" /></p>
<p>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</p>
+You can find the Javadoc here: <a
href="http://olingo.apache.org/javadoc/odata4/index.html";>http://olingo.apache.org/javadoc/odata4/index.html</a></p>
<h3 id="413-implement-the-required-methods">4.1.3. Implement the required
methods</h3>
<p>The base class <em>EdmProvider</em> provides methods for declaring the
metadata of all OData elements.</p>
<p>For example:
@@ -743,11 +743,11 @@ The servlet is a standard <em>HttpServle
<p>Create a new package <em>myservice.mynamespace.web</em>.
Create Java class with name <em>DemoServlet</em> that inherits from
<em>HttpServlet</em>.</p>
<p><img alt="createJavaServletClass" src="createJavaServletClass.png"
title="Creating the servlet class" /></p>
-<p>Override the <em>service()</em> method.<br />
+<p>Override the <code>service()</code> method.<br />
Basically, what weâre doing here is to create an <em>ODataHttpHandler</em>,
which is a class that is provided by <em>Olingo</em>.
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 <em>ODataHttpHandler</em> needs to carry the knowledge about
the <em>EdmProvider</em>.</p>
+Furthermore, the <code>ODataHttpHandler</code> needs to carry the knowledge
about the <code>EdmProvider</code>.</p>
<p>As such, hereâs the location where our 2 implemented classes come
together, the metadata declaration and the data provisioning.</p>
<div class="codehilite"><pre><span class="c1">// This class represents a
standard HttpServlet implementation.</span>
<span class="c1">// It is used as main entry point for the web application
that carries the OData service.</span>
@@ -901,10 +901,10 @@ If you face problems related to the serv
Our first OData service is very simple; it only allows invoking one entity
collection, apart from the service document and the metadata document.</p>
<p><strong>Outlook</strong></p>
<p>Further topics to be covered by follow-up tutorials:<br />
-<em> READ scenario: reading single entity, reading property<br />
-</em> WRITE scenario: executing PUT, POST and DELETE requests<br />
-<em> Navigation: navigating from one entity to a corresponding second entity
-</em> Data types</p>
+ * READ scenario: reading single entity, reading property<br />
+ * WRITE scenario: executing PUT, POST and DELETE requests<br />
+ * Navigation: navigating from one entity to a corresponding second entity
+ * Data types</p>
<p><strong>Further reading</strong></p>
<p>OData specification: <a href="http://odata.org/";>http://odata.org/</a><br />
Olingo Javadoc: <a
href="http://olingo.apache.org/javadoc/odata4/index.html";>http://olingo.apache.org/javadoc/odata4/index.html</a></p><div
align="center">
