olingo-commits mailing list archives

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

URL: http://svn.apache.org/r1523668
CMS commit to olingo by jhuesken


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=1523668&r1=1523667&r2=1523668&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:22:18 2013
@@ -146,6 +146,6 @@ This section explains how to enable cust
 4. Register the class created in step 3 with *ODataJPAContext* as shown below. The registration
can be done during the initialization of *ODataJPAContext* in OData JPA Service Factory along
with initializing persistence unit name, entity manager factory instance and optional mapping
- 	   oDataJPAContext.setJPAEdmExtension((JPAEdmExtension) new SalesOrderProcessingExtension());
+        oDataJPAContext.setJPAEdmExtension((JPAEdmExtension) new SalesOrderProcessingExtension());
 	*Note*: You must register the class because the OData JPA Processor Library should be informed
about the list of Java methods that it needs to process in a project. If we do not register,
then OData JPA Processor Library should scan all the classes and the methods in the Java project
looking for EDM annotations. In order to avoid such overload, it is mandatory to specify the
list of Java methods that shall be transformed into function imports in a class.
\ No newline at end of file

View raw message