svn commit: r1549796 - /incubator/olingo/site/trunk/content/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext

[sk...@apache.org]

Author: sklevenz
Date: Tue Dec 10 09:36:37 2013
New Revision: 1549796

URL: http://svn.apache.org/r1549796
Log:
CMS commit to olingo by sklevenz

Modified:
    incubator/olingo/site/trunk/content/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext

Modified: incubator/olingo/site/trunk/content/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext
URL: http://svn.apache.org/viewvc/incubator/olingo/site/trunk/content/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext?rev=1549796&r1=1549795&r2=1549796&view=diff
==============================================================================
--- incubator/olingo/site/trunk/content/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext (original)
+++ incubator/olingo/site/trunk/content/doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext Tue Dec 10 09:36:37 2013
@@ -20,13 +20,13 @@ Notice:    Licensed to the Apache Softwa
 
 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.
 
-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.
+Some service providers would like to get control over the path hierarchy. This is called service resolution. Actually it means an OData path can start at any hierarchy path level behind the service mapping path elements.
 
-A uri schema with and without service resolution is shown here: 
+An uri schema with and without service resolution is shown here: 
 
 ![Picture: Service Resolution](/img/service-resolution-url.png)
 
-A service inti parameter (`org.apache.olingo.odata2.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>. 
+A service init parameter (`org.apache.olingo.odata2.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 value is 2 and the resulting service resolution uses two path segments. The first one is for <namespace> and the secound for <service>. 
 
     <?xmlversion="1.0"encoding="UTF-8"?>
     <web-appxmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -60,7 +60,7 @@ A service inti parameter (`org.apache.ol
        </servlet-mapping>
     </web-app>
 
-A processor implementation (e.g. `ODataSingleProcessor`) does have access to a `ODataContext` object which will deliver a `ODataUriInfo` object. From this class a processor implementation can access the service resolution information which is as following: 
+A processor implementation (e.g. `ODataSingleProcessor`) does have access to an `ODataContext` object which will deliver a `ODataUriInfo` object. From this class a processor implementation can access the service resolution information which is as following: 
 
 - URI: *http://localhost:8080/odata.svc/[namespace]/[system]/Room('1')/Size/$value*  
 - preceding path segments:	*[namespace], [system]*