svn commit: r1000171 - in /websites/staging/deltaspike/trunk/content: ./ documentation/data.html

[bu...@apache.org]

Author: buildbot
Date: Mon Oct 31 01:06:47 2016
New Revision: 1000171

Log:
Staging update by buildbot for deltaspike

Modified:
    websites/staging/deltaspike/trunk/content/   (props changed)
    websites/staging/deltaspike/trunk/content/documentation/data.html

Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Oct 31 01:06:47 2016
@@ -1 +1 @@
-1766912
+1767212

Modified: websites/staging/deltaspike/trunk/content/documentation/data.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/documentation/data.html (original)
+++ websites/staging/deltaspike/trunk/content/documentation/data.html Mon Oct 31 01:06:47 2016
@@ -275,7 +275,7 @@ table.CodeRay td.code>pre{padding:0}
 <h2 id="_overview">Overview</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>The Data module provides capabilities for implementing repository patterns and thereby simplifying the repository layer. Repository patterns are ideal for simple queries that require boilerplate code, enabling cenertalization of query logic and consequently reducing code duplication and improving testability.</p>
+<p>The Data module provides capabilities for implementing repository patterns and thereby simplifying the repository layer. Repository patterns are ideal for simple queries that require boilerplate code, enabling centralization of query logic and consequently reducing code duplication and improving testability.</p>
 </div>
 <div class="paragraph">
 <p>The code sample below gives you a quick overview on the common usage
@@ -321,7 +321,7 @@ parameters.</p>
 <div class="paragraph">
 <p>The implementation of the method is done automatically by the CDI
 extension. A client can declare a dependency to the interface only. The
-details on how to use those features are outlines in the following
+details on how to use those features are outlined in the following
 chapters.</p>
 </div>
 </div>
@@ -1068,7 +1068,7 @@ more control on the generated query.</p>
 <div class="sect2">
 <h3 id="_using_query_annotations">Using Query Annotations</h3>
 <div class="paragraph">
-<p>The simples way to define a specific query is by annotating a method and
+<p>The simplest way to define a specific query is by annotating a method and
 providing the JPQL query string which has to be executed. In code, this
 looks like the following sample:</p>
 </div>
@@ -1282,7 +1282,7 @@ expressions.</p>
 <i class="fa icon-important" title="Important"></i>
 </td>
 <td class="content">
-<code>QueryResult</code> is based on our internal understanding of your query
+<code>QueryResult</code> is based on our internal understanding of your query.
 DeltaSpike expects the alias used in your queries to refer to the entity as <code>e</code>
 You can disable this behavior by passing in false with your attribute, <code>.orderDesc("p.age", false)</code>
 which would add descending ordering to your existing query <code>select p from Person p</code>
@@ -1501,7 +1501,7 @@ currently recommend creating an extensio
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="CodeRay highlight"><code data-lang="java"><span class="directive">public</span> <span class="type">class</span> <span class="class">TxExtension</span>&lt;E&gt; <span class="directive">implements</span> TxRepository <span class="comment">// this is your extension interface</span>
+<pre class="CodeRay highlight"><code data-lang="java"><span class="directive">public</span> <span class="type">class</span> <span class="class">TxExtension</span>&lt;E&gt; <span class="directive">implements</span> DelegateQueryHandler, TxRepository <span class="comment">// this is your extension interface</span>
 {
     <span class="annotation">@Inject</span>
     <span class="directive">private</span> EntityManager em;
@@ -1528,7 +1528,7 @@ implementation can be, for example, in a
 <div class="sect2">
 <h3 id="_query_delegates">Query Delegates</h3>
 <div class="paragraph">
-<p>While repositories defines several base interfaces, there might still be
+<p>While several base interfaces are defined for repositories, there might still be
 the odd convenience method that is missing. This is actually intentional
 - things should not get overloaded for each and every use case. That&#8217;s
 why in DeltaSpike you can define your own reusable methods.</p>
@@ -1650,7 +1650,7 @@ interface:</p>
     ...
 
     <span class="annotation">@Override</span>
-    <span class="directive">public</span> <span class="predefined-type">Object</span> mapResultList(<span class="predefined-type">List</span>&lt;Simple&gt; result)
+    <span class="directive">public</span> <span class="predefined-type">Object</span> mapResultList(<span class="predefined-type">List</span>&lt;Person&gt; result)
     {
         ... <span class="comment">// result lists can also be mapped into something different</span>
             <span class="comment">// than a collection.</span>
@@ -1707,7 +1707,7 @@ correctly (in this example, a conversion
 <div class="paragraph">
 <p>In many cases it is just required to map a DTO object back and forth. For
 this case, the <code>SimpleQueryInOutMapperBase</code> class can be subclassed,
-which only requires to override two methods:</p>
+which only requires to override three methods:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -1751,7 +1751,7 @@ entity).</p>
 <h2 id="_jpa_criteria_api_support">JPA Criteria API Support</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Beside automatic query generation, the DeltaSpike Data module also
+<p>Besides automatic query generation, the DeltaSpike Data module also
 provides a DSL-like API to create JPA 2 Criteria queries. It takes
 advantage of the JPA 2 meta model, which helps creating type safe
 queries.</p>