You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@olingo.apache.org by ch...@apache.org on 2015/10/21 09:56:30 UTC

svn commit: r1709739 - /olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext

Author: chrish
Date: Wed Oct 21 07:56:30 2015
New Revision: 1709739

URL: http://svn.apache.org/viewvc?rev=1709739&view=rev
Log:
CMS commit to olingo by chrish

Modified:
    olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext

Modified: olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext
URL: http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext?rev=1709739&r1=1709738&r2=1709739&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext (original)
+++ olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext Wed Oct 21 07:56:30 2015
@@ -25,7 +25,7 @@ Notice:    Licensed to the Apache Softwa
 
 [TOC]
 
-## 1. Introduction
+## Introduction
 
 In the present tutorial, we’ll implement a function import and an action import as well.
 
@@ -113,7 +113,7 @@ The parameters are passed within the bod
 
 As you read in the definition, actions can have side effects (modifying the data) but cannot be composed like functions.
 
-# 2. Preparation
+## Preparation
 
 You should read the previous tutorials first to have an idea how to read entities and entity collections. In addition the following code is based on the write tutorial merged with the navigation tutorial.
 
@@ -121,7 +121,7 @@ As a shortcut you should checkout the pr
 
 Afterwards do a Deploy and run: it should be working. At this state you can perform CRUD operations and do navigations between products and categories.
 
-## 3.1 Implementation
+## Implementation
 
 We will using the given data model you are familiar with. To keep things simple we implement one function import and one action import.
 
@@ -158,7 +158,7 @@ While actions are called by using HTTP M
   * Extend the entity collection and the entity processor to handle function imports
   * Implement an action processor
 
-### 3.1 Extend the Metadata model
+### Extend the Metadata model
 
 Create the following constants in the DemoEdmProvider. These constants are used to address the operations.
 
@@ -302,7 +302,7 @@ Also add the following lines to the meth
     entityContainer.setActionImports(actionImports);
 
 
-## 3.2 Extend the data store
+## Extend the data store
 
 We need two methods in the data store to read the function import `CountCategories`.
 
@@ -381,7 +381,7 @@ We also create two methods to reset the
     }
 
 
-## 3.3 Extend the entity collection and the entity processor to handle function imports
+## Extend the entity collection and the entity processor to handle function imports
 
 We start with the entity collection processor `DemoEntityCollectionProcessor`.
 To keep things simple, the first steps is to distinguish between entity collections and function imports.
@@ -494,7 +494,7 @@ Next we will implement the processor to
     }
 
 
-### 3.4 Implement an action processor
+### Implement an action processor
 
 Create a new class `DemoActionProcessor` make them implement the interface `ActionVoidProcessor`.
 
@@ -552,7 +552,7 @@ Execute the action and set the response
       response.setStatusCode(HttpStatusCode.NO_CONTENT.getStatusCode());
     }
 
-## 4. Run the implemented service
+## Run the implemented service
 
 After building and deploying your service to your server, you can try the following requests:
 
@@ -581,7 +581,7 @@ After building and deploying your servic
 To verify that the service has been reseted, you can request the collection of products
 
 * [http://localhost:8080/DemoService-Action/DemoService.svc/Products](http://localhost:8080/DemoService-Action/DemoService.svc/Products)
-# 5. Links
+# Links
 
 ### Tutorials