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:14:15 UTC
svn commit: r888916 - in /websites/staging/olingo/trunk/content: ./
doc/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html
Author: buildbot
Date: Tue Dec 3 12:14:15 2013
New Revision: 888916
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:14:15 2013
@@ -1 +1 @@
-1547360
+1547361
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:14:15 2013
@@ -75,13 +75,13 @@
<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><img alt="Picture: Service Resolution" src="/img/service-resolution-url.png" /></p>
-<p>A service inti parameter (<code>com.sap.core.odata.path.split</code>) 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>
+<p>A service inti parameter (<code>org.apache.olingo.odata2.path.split</code>) 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>
<span class="na">xmlns=</span><span class="s">"http://java.sun.com/xml/ns/javaee"</span><span class="na">xmlns:web=</span><span class="s">"http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"</span>
<span class="na">xsi:schemaLocation=</span><span class="s">"http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"</span>
<span class="na">id=</span><span class="s">"WebApp_ID"</span><span class="na">version=</span><span class="s">"2.5"</span><span class="nt">></span>
- <span class="nt"><display-name></span>org.odata4j.ext.web<span class="nt"></display-name></span>
+ <span class="nt"><display-name></span>MyApp<span class="nt"></display-name></span>
<span class="nt"><welcome-file-list></span>
<span class="nt"><welcome-file></span>index.jsp<span class="nt"></welcome-file></span>
<span class="nt"></welcome-file-list></span>
@@ -90,14 +90,14 @@
<span class="nt"><servlet-class></span>org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet<span class="nt"></servlet-class></span>
<span class="nt"><init-param></span>
<span class="nt"><param-name></span>javax.ws.rs.Application<span class="nt"></param-name></span>
- <span class="nt"><param-value></span>com.sap.core.odata.core.ODataApplication<span class="nt"></param-value></span>
+ <span class="nt"><param-value></span>org.apache.olingo.odata2.core.ODataApplication<span class="nt"></param-value></span>
<span class="nt"></init-param></span>
<span class="nt"><init-param></span>
- <span class="nt"><param-name></span>com.sap.core.odata.service.factory<span class="nt"></param-name></span>
- <span class="nt"><param-value></span>com.sap.core.odata.ref.processor.ScenarioServiceFactory<span class="nt"></param-value></span>
+ <span class="nt"><param-name></span>org.apache.olingo.odata2.service.factory<span class="nt"></param-name></span>
+ <span class="nt"><param-value></span>org.apache.olingo.odata2.ref.processor.ScenarioServiceFactory<span class="nt"></param-value></span>
<span class="nt"></init-param></span>
<span class="nt"><init-param></span>
- <span class="nt"><param-name></span>com.sap.core.odata.path.split<span class="nt"></param-name></span>
+ <span class="nt"><param-name></span>org.apache.olingo.odata2.path.split<span class="nt"></param-name></span>
<span class="nt"><param-value></span>2<span class="nt"></param-value></span>
<span class="nt"></init-param></span>
<span class="nt"><load-on-startup></span>1<span class="nt"></load-on-startup></span>