svn commit: r914549 - in /websites/staging/olingo/trunk/content: ./ doc/tutorials/HandlingClobAndBlob.html

[bu...@apache.org]

Author: buildbot
Date: Tue Jul  1 07:53:13 2014
New Revision: 914549

Log:
Staging update by buildbot for olingo

Modified:
    websites/staging/olingo/trunk/content/   (props changed)
    websites/staging/olingo/trunk/content/doc/tutorials/HandlingClobAndBlob.html

Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul  1 07:53:13 2014
@@ -1 +1 @@
-1606999
+1607001

Modified: websites/staging/olingo/trunk/content/doc/tutorials/HandlingClobAndBlob.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/tutorials/HandlingClobAndBlob.html (original)
+++ websites/staging/olingo/trunk/content/doc/tutorials/HandlingClobAndBlob.html Tue Jul  1 07:53:13 2014
@@ -79,20 +79,22 @@
 <p>entities. Following is the proposal on how OData JPA Processor Library handles java.sql.Blob and java.sql.Clob during metadata generation and runtime processing. </p>
 <h3 id="edm-generation">EDM Generation</h3>
 <p>Based on the JPA entity property type, the pseudocode for generating the EDM is as below.</p>
-<p>For java.sql.Blob:</p>
+<p><strong>For java.sql.Blob</strong>:</p>
 <ol>
 <li>Check if JPA entity property is of type byte[] or of type java.sql.Blob and annotated with @Lob annotation. </li>
 <li>If Step 1 is true, then generate an EDM property with type as Edm.Binary</li>
 </ol>
-<p>For java.sql.Clob:</p>
+<p><strong>For java.sql.Clob</strong>:</p>
 <ol>
 <li>Check if JPA entity property is of type java.sql.Clob and annotated with @Lob annotation. </li>
 <li>If Step 1 is true, then generate an EDM property with type as Edm.String (with no max length unless a max length is specified). </li>
 </ol>
 <h3 id="runtime-processing">Runtime Processing</h3>
-<p><strong>Prerequisite:</strong>
-1. It is mandatory to implement the callback interface org.apache.olingo.odata2.jpa.processor.api.OnJPAWriteContent.
-2. The implemented interface needs to be registered with the service via the method 'setOnJPAWriteContent' part of 'ODataJPAServiceFactory'. </p>
+<p><strong>Prerequisite:</strong></p>
+<ol>
+<li>It is mandatory to implement the callback interface org.apache.olingo.odata2.jpa.processor.api.OnJPAWriteContent.</li>
+<li>The implemented interface needs to be registered with the service via the method 'setOnJPAWriteContent' part of 'ODataJPAServiceFactory'. </li>
+</ol>
 <p>Following is the pseudocode for handling the java.sql.Blob and java.sql.Clob during runtime.</p>
 <div class="codehilite"><pre>    <span class="o">/*</span> <span class="n">Callback</span> <span class="n">Implementation</span> <span class="o">*/</span>
 
@@ -143,10 +145,12 @@
 </pre></div>
 
 
-<p>OData JPA Processor Library internally does the following:
-1. Checks if the JPA entity property is of type java.sql.Blob or java.sql.Clob.
-2. If Step 1 is true, then it invokes the registered callback method 'getJPABlob' or 'getJPAClob' respectively.
-3. If callback method is not defined, it throws an exception. </p>
+<p>OData JPA Processor Library internally does the following:</p>
+<ol>
+<li>Checks if the JPA entity property is of type java.sql.Blob or java.sql.Clob.</li>
+<li>If Step 1 is true, then it invokes the registered callback method 'getJPABlob' or 'getJPAClob' respectively.</li>
+<li>If callback method is not defined, it throws an exception. </li>
+</ol>
 <p><em>Note</em>: Step 3 is needed because the OData JPA Processor Library is not bound to any specific implementation of Blob or Clob interface. </p>