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:22:27 UTC
svn commit: r878627 - in /websites/staging/olingo/trunk/content: ./
doc/tutorials/jpafunctionimport.html
Author: buildbot
Date: Mon Sep 16 14:22:27 2013
New Revision: 878627
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:22:27 2013
@@ -1 +1 @@
-1523665
+1523668
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:22:27 2013
@@ -207,7 +207,10 @@
</li>
<li>
<p>Register the class created in step 3 with <em>ODataJPAContext</em> as shown below. The registration can be done during the initialization of <em>ODataJPAContext</em> in OData JPA Service Factory along with initializing persistence unit name, entity manager factory instance and optional mapping model.</p>
-<p>oDataJPAContext.setJPAEdmExtension((JPAEdmExtension) new SalesOrderProcessingExtension());</p>
+<div class="codehilite"><pre><span class="n">oDataJPAContext</span><span class="p">.</span><span class="n">setJPAEdmExtension</span><span class="p">((</span><span class="n">JPAEdmExtension</span><span class="p">)</span> <span class="n">new</span> <span class="n">SalesOrderProcessingExtension</span><span class="p">());</span>
+</pre></div>
+
+
<p><em>Note</em>: 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.</p>
</li>
</ol>