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 2014/02/25 08:58:27 UTC

svn commit: r899115 - in /websites/staging/olingo/trunk/content: ./ doc/tutorials/jpafunctionimport.html

Author: buildbot
Date: Tue Feb 25 07:58:26 2014
New Revision: 899115

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 Tue Feb 25 07:58:26 2014
@@ -1 +1 @@
-1571269
+1571599

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 Tue Feb 25 07:58:26 2014
@@ -76,7 +76,6 @@
 <hr />
 <p>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>
 <p>OData JPA Processor Library is enhanced to:</p>
-<p>Enable</p>
 <ul>
 <li>
 <p>Enable Custom Operations as Function Imports</p>