You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@olingo.apache.org by bu...@apache.org on 2015/08/13 13:47:19 UTC
svn commit: r961714 - in /websites/staging/olingo/trunk/content: ./
doc/odata4/tutorials/sqo_es/tutorial_sqo_es.html
Author: buildbot
Date: Thu Aug 13 11:47:19 2015
New Revision: 961714
Log:
Staging update by buildbot for olingo
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/doc/odata4/tutorials/sqo_es/tutorial_sqo_es.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Aug 13 11:47:19 2015
@@ -1 +1 @@
-1695682
+1695684
Modified: websites/staging/olingo/trunk/content/doc/odata4/tutorials/sqo_es/tutorial_sqo_es.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/odata4/tutorials/sqo_es/tutorial_sqo_es.html (original)
+++ websites/staging/olingo/trunk/content/doc/odata4/tutorials/sqo_es/tutorial_sqo_es.html Thu Aug 13 11:47:19 2015
@@ -256,17 +256,17 @@ The drawback of this implementation is,
<p>In order to understand the <code>$expand</code> system query option, letâs first quickly recap what weâve learned in the navigation-tutorial:</p>
<ol>
<li>
-<p>In order to be able to navigate from one entity to another entity, we need at least 2 EntityTypes and at least one NavigationProperty
- <img alt="Metadata" src="metadataNav.jpg" title="Declaring the navigation in the metadata" /></p>
+<p>In order to be able to navigate from one entity to another entity, we need at least 2 EntityTypes and at least one NavigationProperty<br />
+<img alt="Metadata" src="metadataNav.jpg" title="Declaring the navigation in the metadata" /></p>
</li>
<li>
-<p>We can invoke one single entity, e.g. display one product:
- <img alt="Products(1)SingleRead" src="responseProducts_1.jpg" title="The result of a single read" /></p>
+<p>We can invoke one single entity, e.g. display one product:<br />
+<img alt="Products(1)SingleRead" src="responseProducts_1.jpg" title="The result of a single read" /></p>
</li>
<li>
<p>And we can follow the navigation to the second entity, by appending the navigation property name, e.g. invoke the category of that product.
- As weâve seen in the metadata above, the name of the navigation property is <em>Category</em>
- <img alt="Products(1)NavToCat" src="responseProducts_1_navCat.jpg" title="Navigating from a Product to its Category" /></p>
+ As weâve seen in the metadata above, the name of the navigation property is <em>Category</em><br />
+<img alt="Products(1)NavToCat" src="responseProducts_1_navCat.jpg" title="Navigating from a Product to its Category" /></p>
</li>
</ol>
<p>We have executed two requests to our OData service, in order to obtain the data for the product and for its related category.<br />
@@ -429,8 +429,8 @@ The complete <code>readEntity(...)</code
<p>Expand an navigation with only the first entity:</p>
<ul>
<li><a href="http://localhost:8080/DemoService/DemoService.svc/Categories?$expand=Products($top=1)">http://localhost:8080/DemoService/DemoService.svc/Categories?$expand=Products($top=1)</a>
-<strong>NOTE:</strong> In current <code>4.0.0-beta-03</code> version of Olingo is a minor bug which prevents the expand of a navigation which has the same name as an EntitySet (see <a href="https://issues.apache.org/jira/browse/OLINGO-741">OLINGO-741</a>).
-Hence above link will work with latest SNAPSHOT version or the final <code>4.0.0</code> release.</li>
+ <strong>NOTE:</strong> In current <code>4.0.0-beta-03</code> version of Olingo is a minor bug which prevents the expand of a navigation which has the same name as an EntitySet (see <a href="https://issues.apache.org/jira/browse/OLINGO-741">OLINGO-741</a>).
+ Hence above link will work with latest SNAPSHOT version or the final <code>4.0.0</code> release.</li>
</ul>
</li>
<li>
@@ -485,10 +485,10 @@ Like described in section 3.1, the Oling
<li>
<p>Using <code>$expand</code></p>
<ul>
-<li><a href="http://localhost:8080/DemoService/DemoService.svc/Products(1)?$expand=Category">http://localhost:8080/DemoService/DemoService.svc/Products(1)?$expand=Category</a></li>
-<li><a href="http://localhost:8080/DemoService/DemoService.svc/Products(1)?$expand=Category">http://localhost:8080/DemoService/DemoService.svc/Products(1)?$expand=Category</a></li>
-<li><a href="http://localhost:8080/DemoService/DemoService.svc/Categories(1)?$expand=Products">http://localhost:8080/DemoService/DemoService.svc/Categories(1)?$expand=Products</a>
- <strong>NOTE:</strong> In current <code>4.0.0-beta-03</code> version of Olingo is a minor bug which prevents the expand of a navigation which has the same name as an EntitySet (see <a href="https://issues.apache.org/jira/browse/OLINGO-741">OLINGO-741</a>).
+<li><a href="http://localhost:8080/DemoService/DemoService.svc/Products(1)?$expand=Category">http://localhost:8080/DemoService/DemoService.svc/Products(1)?$expand=Category</a> </li>
+<li><a href="http://localhost:8080/DemoService/DemoService.svc/Products(1)?$expand=Category">http://localhost:8080/DemoService/DemoService.svc/Products(1)?$expand=Category</a> </li>
+<li><a href="http://localhost:8080/DemoService/DemoService.svc/Categories(1)?$expand=Products">http://localhost:8080/DemoService/DemoService.svc/Categories(1)?$expand=Products</a><br />
+<strong>NOTE:</strong> In current <code>4.0.0-beta-03</code> version of Olingo is a minor bug which prevents the expand of a navigation which has the same name as an EntitySet (see <a href="https://issues.apache.org/jira/browse/OLINGO-741">OLINGO-741</a>).
Hence above link will work with latest SNAPSHOT version or the final <code>4.0.0</code> release.</li>
<li><a href="http://localhost:8080/DemoService/DemoService.svc/Categories(1)?$expand=*">http://localhost:8080/DemoService/DemoService.svc/Categories(1)?$expand=*</a></li>
</ul>