olingo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r969546 - in /websites/staging/olingo/trunk/content: ./ doc/odata4/tutorials/action/tutorial_action.html
Date Tue, 20 Oct 2015 00:47:54 GMT
Author: buildbot
Date: Tue Oct 20 00:47:53 2015
New Revision: 969546

Log:
Staging update by buildbot for olingo

Modified:
    websites/staging/olingo/trunk/content/   (props changed)
    websites/staging/olingo/trunk/content/doc/odata4/tutorials/action/tutorial_action.html

Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Oct 20 00:47:53 2015
@@ -1 +1 @@
-1709495
+1709496

Modified: websites/staging/olingo/trunk/content/doc/odata4/tutorials/action/tutorial_action.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/odata4/tutorials/action/tutorial_action.html
(original)
+++ websites/staging/olingo/trunk/content/doc/odata4/tutorials/action/tutorial_action.html
Tue Oct 20 00:47:53 2015
@@ -222,7 +222,7 @@ This function takes a mandatory paramete
 
 
 <p>As described in the previous tutorials, the type of the response determines which
processor interface will be called by the Olingo library. It is <strong>important to
know, that functions are dispatched to the traditional processor interfaces</strong>.
-That means there are no special <code>FunctionProcessors</code>. In our case,
the function returns a collection of Categories. So we have to extend the <code>DemoEntityCollectionProcessor</code>.
As you will see it is possible to address a single entity by its  key. So we have to extend
the <code>DemoEntityProcessor</code> as well to handle requests which responds
a single entity.</p>
+That means there are no special "FunctionProcessors". In our case, the function returns a
collection of Categories. So we have to extend the <code>DemoEntityCollectionProcessor</code>.
As you will see it is possible to address a single entity by its  key. So we have to extend
the <code>DemoEntityProcessor</code> as well to handle requests which responds
a single entity.</p>
 <p><strong>Action Import: Reset</strong>  <br />
 This action takes an optional parameter “<em>Amount</em>”. The actions
resets the whole data of the service and creates  <em># of Amount</em> products
with the related categories.</p>
 <p>After finishing the implementation the definition of the action should be like this:</p>



Mime
View raw message