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/09/16 16:24:33 UTC
svn commit: r878628 - in /websites/staging/olingo/trunk/content: ./
doc/tutorials/jpafunctionimport.html
Author: buildbot
Date: Mon Sep 16 14:24:33 2013
New Revision: 878628
Log:
Staging update by buildbot for olingo
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/doc/tutorials/jpafunctionimport.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Sep 16 14:24:33 2013
@@ -1 +1 @@
-1523668
+1523669
Modified: websites/staging/olingo/trunk/content/doc/tutorials/jpafunctionimport.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/tutorials/jpafunctionimport.html (original)
+++ websites/staging/olingo/trunk/content/doc/tutorials/jpafunctionimport.html Mon Sep 16 14:24:33 2013
@@ -69,7 +69,7 @@
- <h1 id="adding-function-imports-to-odata-services">Adding Function Imports to OData Services</h1>
+ <h1 id="adding-function-imports-odata-services-with-the-jpa-processor">Adding Function Imports OData Services with the JPA Processor</h1>
<p>This section explains how to enable custom operations as function imports. Function imports are used to perform custom operations on a JPA entity in addition to CRUD operations. For example, consider a scenario where you would like to check the availability of an item to promise on the sales order line items. ATP check is a custom operation that can be exposed as a function import in the schema of OData service.</p>
<ol>
<li>