You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@olingo.apache.org by jh...@apache.org on 2013/09/16 16:27:25 UTC
svn commit: r1523671 -
/incubator/olingo/site/trunk/content/doc/tutorials/jpafunctionimport.mdtext
Author: jhuesken
Date: Mon Sep 16 14:27:24 2013
New Revision: 1523671
URL: http://svn.apache.org/r1523671
Log:
CMS commit to olingo by jhuesken
Modified:
incubator/olingo/site/trunk/content/doc/tutorials/jpafunctionimport.mdtext
Modified: incubator/olingo/site/trunk/content/doc/tutorials/jpafunctionimport.mdtext
URL: http://svn.apache.org/viewvc/incubator/olingo/site/trunk/content/doc/tutorials/jpafunctionimport.mdtext?rev=1523671&r1=1523670&r2=1523671&view=diff
==============================================================================
--- incubator/olingo/site/trunk/content/doc/tutorials/jpafunctionimport.mdtext (original)
+++ incubator/olingo/site/trunk/content/doc/tutorials/jpafunctionimport.mdtext Mon Sep 16 14:27:24 2013
@@ -16,7 +16,7 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-# Adding Function Imports OData Services with the JPA Processor
+# Adding Function Imports to OData Services with the JPA Processor
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.