You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2017/02/27 14:37:05 UTC

svn commit: r1007371 - in /websites/staging/sling/trunk/content: ./ documentation/bundles/validation.html

Author: buildbot
Date: Mon Feb 27 14:37:05 2017
New Revision: 1007371

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/documentation/bundles/validation.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb 27 14:37:05 2017
@@ -1 +1 @@
-1784572
+1784573

Modified: websites/staging/sling/trunk/content/documentation/bundles/validation.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/bundles/validation.html (original)
+++ websites/staging/sling/trunk/content/documentation/bundles/validation.html Mon Feb 27 14:37:05 2017
@@ -137,12 +137,12 @@ This documentation is still work in prog
 </div>
 <p>Many Sling projects want to be able to validate both Resources and request parameters. Through the Sling Validation Bundle this is possible with the help of validation model resources which define validation rules for a certain resourceType.</p>
 <h1 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h1>
-<p>To use this validation frameworks the following bundles need to be deployed</p>
+<p>To use this validation framework the following bundles need to be deployed</p>
 <ol>
 <li><code>org.apace.sling.validation.api</code></li>
 <li><code>org.apache.sling.validation.core</code></li>
 </ol>
-<p>In addition a <a href="/documentation/the-sling-engine/service-authentication.html">service resolver mapping</a> needs to be configured for the service name <code>org.apache.sling.validation.core</code>. The bound service user needs at least read access to all resource resolver's search paths (usually <code>/apps</code> and <code>/libs</code>).</p>
+<p>In addition a <a href="/documentation/the-sling-engine/service-authentication.html">service resolver mapping</a> needs to be configured for the service name <code>org.apache.sling.validation.core</code>. The bound service user needs to have at least read access to all resources within the resource resolver's search paths (usually <code>/apps</code> and <code>/libs</code>).</p>
 <h1 id="basic-usage">Basic Usage<a class="headerlink" href="#basic-usage" title="Permanent link">&para;</a></h1>
 <p>To validate a resource one first needs to get a <code>ValidationModel</code> and then validate the resource with that model. Both functionalities are provided by the <code>ValidationService</code> OSGi service:</p>
 <div class="codehilite"><pre><span class="k">try</span> <span class="o">{</span>
@@ -339,7 +339,7 @@ That interface defines the method <code>
 <li><a href="http://www.slideshare.net/raducotescu/apache-sling-generic-validation-framework">Apache Sling Generic Validation Framework, adaptTo 2014</a></li>
 </ol>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1784572 by kwin on Mon, 27 Feb 2017 14:35:12 +0000
+        Rev. 1784573 by kwin on Mon, 27 Feb 2017 14:36:56 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project