Author: mibo
Date: Mon Apr 18 19:56:56 2016
New Revision: 1739813
URL: http://svn.apache.org/viewvc?rev=1739813&view=rev
Log:
Updated PathInfo
Modified:
olingo/site/trunk/content/doc/odata2/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext
Modified:
olingo/site/trunk/content/doc/odata2/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext
URL:
http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata2/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext?rev=1739813&r1=1739812&r2=1739813&view=diff
==============================================================================
---
olingo/site/trunk/content/doc/odata2/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext
(original)
+++
olingo/site/trunk/content/doc/odata2/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.mdtext
Mon Apr 18 19:56:56 2016
@@ -16,17 +16,17 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-# Service Resolution
+# Service Resolution
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. This
is called service resolution. Actually it means an OData path can start at any
hierarchy path level behind the service mapping path elements.
-An uri schema with and without service resolution is shown here:
+An uri schema with and without service resolution is shown here:
-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>.
+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 init parameter (`org.apache.ol
</servlet-mapping>
</web-app>
-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:
+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]*
@@ -71,12 +71,12 @@ A processor implementation (e.g. `ODataS
public interface ODataContext {
ODataService getService() throws ODataException;
- ODataUriInfo getUriInfo() throws ODataException;
+ PathInfo getPathInfo() throws ODataException;
}
-
- public interface ODataUriInfo {
- List<ODataPathSegment> getPrecedingPathSegmentList();
- List<ODataPathSegment> getODataPathSegmentList();
- URI getBaseUri();
+
+ public interface PathInfo {
+ List<PathSegment> getPrecedingSegments();
+ List<PathSegment> getODataSegments();
+ URI getServiceRoot();
+ URI getRequestUri();
}
-
