olingo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r914550 - in /websites/staging/olingo/trunk/content: ./ doc/tutorials/HandlingClobAndBlob.html
Date Tue, 01 Jul 2014 08:00:44 GMT
Author: buildbot
Date: Tue Jul  1 08:00:44 2014
New Revision: 914550

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 08:00:44 2014
@@ -1 +1 @@
-1607001
+1607005

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 08:00:44 2014
@@ -74,28 +74,28 @@
             
             
             <h2 id="handling-blob-and-clob-data-types">Handling BLOB and CLOB Data
Types</h2>
-<p>JPA entities can have properties that are of type java.sql.Blob or java.sql.Clob.
Internally, JPA entities can instantiate a JPA provider (Eclipse Link or Hibernate or ...)
specific implementation </p>
-<p>of the above two interfaces and bind them to the properties. To enable write on
such properties using OData JPA Processor Library, an additional access modifier is required
to be added to the JPA </p>
-<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>
+<p>JPA entities can have properties that are of type <code>java.sql.Blob</code>
or <code>java.sql.Clob</code>. Internally, JPA entities can instantiate a JPA
provider (Eclipse Link or Hibernate or ...) specific implementation
+of the above two interfaces and bind them to the properties. To enable write on such properties
using OData JPA Processor Library, an additional access modifier is required to be added to
the JPA 
+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><strong>For java.sql.Blob</strong>:</p>
+<p><strong>For <code>java.sql.Blob</code></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><strong>For java.sql.Clob</strong>:</p>
+<p><strong>For <code>java.sql.Clob</code></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>
+<li>Check if JPA entity property is of type <code>java.sql.Clob</code>
and annotated with @Lob annotation. </li>
+<li>If Step 1 is true, then generate an EDM property with type as <code>Edm.String</code>
(with no max length unless a max length is specified). </li>
 </ol>
 <h3 id="runtime-processing">Runtime Processing</h3>
-<p><strong>Prerequisite:</strong></p>
+<p><strong>Prerequisites:</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>
+<li>It is mandatory to implement the callback interface <code>org.apache.olingo.odata2.jpa.processor.api.OnJPAWriteContent</code>.</li>
+<li>The implemented interface needs to be registered with the service via the method
<code>setOnJPAWriteContent</code> part of <code>ODataJPAServiceFactory</code>.
</li>
 </ol>
-<p>Following is the pseudocode for handling the java.sql.Blob and java.sql.Clob during
runtime.</p>
+<p>Following is the pseudocode for handling the <code>java.sql.Blob</code>
and <code>java.sql.Clob</code> 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>
 
     <span class="n">public</span> <span class="n">class</span> <span
class="n">OnDBWriteContent</span> <span class="n">implements</span> <span
class="n">OnJPAWriteContent</span> <span class="p">{</span>
@@ -147,11 +147,11 @@
 
 <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>Checks if the JPA entity property is of type <code>java.sql.Blob</code>
or <code>java.sql.Clob</code>.</li>
+<li>If Step 1 is true, then it invokes the registered callback method <code>getJPABlob</code>
or <code>getJPAClob</code> 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>
+<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>
             
             
             



Mime
View raw message