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

[ch...@apache.org]

Author: chrish
Date: Tue Oct  6 11:27:40 2015
New Revision: 1706998

URL: http://svn.apache.org/viewvc?rev=1706998&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=1706998&r1=1706997&r2=1706998&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 Tue Oct  6 11:27:40 2015
@@ -132,7 +132,7 @@ Afterwards do a Deploy and run: it shoul
 
 We`ll using the given data model you are familiar with. To keep things simple we implement one function import and one action import.
 
-**Function Import: CountCategories**
+**Function Import: CountCategories**    
 This function takes a mandatory parameter “Amount”. The function returns a collection of categories with the very same number of related products.
 
 After finishing the implementation the definition of the function should look like this:
@@ -145,7 +145,7 @@ After finishing the implementation the d
 
 As described in the previous tutorials, the type of the response determines which processor interface will be called by the Olingo library. It is important to know, that functions are dispatched to the traditional processor interfaces. That means there are no special “FunctionProcessors”. In our case, the function returns a collection of Categories. So we have to extend the *DemoEntityCollectionProcessor*. As you will see it is possible to address a single entity by it`s  key. So we have to extend the DemoEntityProcessor as well to handle requests which responds a single entity.
 
-**Action Import: Reset**
+**Action Import: Reset**    
 This action takes an optional parameter “Amount”. The actions resets the whole data of the service and creates at most #Amount products with the related categories.
 
 After finishing the implementation the definition of the action should be like this: 
@@ -157,11 +157,11 @@ After finishing the implementation the d
 
 While actions are called by using HTTP Method POST is nessesary to introduce new processor interfaces for actions. So there exists a bunch of interfaces, for each return type strictly one.
 
-**Steps**
- - Extent the Metadata model
- - Extent the data store
- - Extent the entity collection and the entity processor to handle function imports
- - Implement an action processor
+**Steps**    
+ * Extent the Metadata model
+ * Extent the data store
+ * Extent the entity collection and the entity processor to handle function imports
+ * Implement an action processor
 
 ## 3.1 Extent the Metadata model