olingo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jhues...@apache.org
Subject svn commit: r1523665 - /incubator/olingo/site/trunk/content/doc/tutorials/jpafunctionimport.mdtext
Date Mon, 16 Sep 2013 14:20:58 GMT
Author: jhuesken
Date: Mon Sep 16 14:20:58 2013
New Revision: 1523665

URL: http://svn.apache.org/r1523665
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=1523665&r1=1523664&r2=1523665&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:20:58 2013
@@ -140,7 +140,7 @@ This section explains how to enable cust
           public void extendWithOperation(final JPAEdmSchemaView view) {
             view.registerOperations(SalesOrderHeaderProcessor.class, null);
           }
-       }
+        }
 
  	*Note*: Use the method *extendWithOperation* to register the list of classes and the methods
within the class that needs to be exposed as Function Imports. If the second parameter is
passed null, then the OData JPA Processor Library would consider all the annotated methods
within the class for Function Import. However, you could also restrict the list of methods
that needs to be transformed into function imports within a Java class by passing an array
of Java method names as the second parameter.
 



Mime
View raw message