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 2013/12/03 13:05:37 UTC
svn commit: r888910 - in /websites/staging/olingo/trunk/content: ./
doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html
Author: buildbot
Date: Tue Dec 3 12:05:37 2013
New Revision: 888910
Log:
Staging update by buildbot for olingo
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Dec 3 12:05:37 2013
@@ -1 +1 @@
-1547354
+1547356
Modified: websites/staging/olingo/trunk/content/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html (original)
+++ websites/staging/olingo/trunk/content/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html Tue Dec 3 12:05:37 2013
@@ -74,7 +74,8 @@
<p>An OData service usually starts with "/" which delivers the service document while all preceding path segments belong to the servlet and servlet mapping of a web application.</p>
<p>Some service providers would like to get control over the path hierarchy and we call this service resolution. Actually it means a OData path can start on any hierarchy path level after the service mapping.</p>
<p>A uri schema with and without service resolution is shown here: </p>
-<p><strong>[Graphic: tbd]</strong></p>
+<p><img alt="xxx" src="img/service-resolution-url.png" /></p>
+<p><img alt="alt text" src="img/service-resolution-url.png" /></p>
<p>A service inti parameter (com.sap.core.odata.path.split) can be set for servlet configuration (see web.xml) and define how many path segments are not interpreted as OData path segments. In the example the split is 2 and the resulting service resolution uses two segments for <namespace> and <service>. </p>
<div class="codehilite"><pre><span class="cp"><?xmlversion="1.0"encoding="UTF-8"?></span>
<span class="nt"><web-appxmlns:xsi</span><span class="err">="http://www.w3.org/2001/XMLSchema-instance"</span>