Return-Path: 
 <commits-return-10922-apmail-sling-commits-archive=sling.apache.org@sling.apache.org>
X-Original-To: apmail-sling-commits-archive@www.apache.org
Delivered-To: apmail-sling-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 752E89B3E
	for <apmail-sling-commits-archive@www.apache.org>;
 Sun, 22 Apr 2012 17:50:56 +0000 (UTC)
Received: (qmail 84754 invoked by uid 500); 22 Apr 2012 17:50:56 -0000
Delivered-To: apmail-sling-commits-archive@sling.apache.org
Received: (qmail 84687 invoked by uid 500); 22 Apr 2012 17:50:56 -0000
Mailing-List: contact commits-help@sling.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@sling.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@sling.apache.org>
List-Post: <mailto:commits@sling.apache.org>
List-Id: <commits.sling.apache.org>
Reply-To: dev@sling.apache.org
Delivered-To: mailing list commits@sling.apache.org
Received: (qmail 84677 invoked by uid 99); 22 Apr 2012 17:50:56 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Apr 2012 17:50:56 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Apr 2012 17:50:52 +0000
Received: from eris.apache.org (localhost [127.0.0.1])
	by eris.apache.org (Postfix) with ESMTP id BF4D823889D5
	for <commits@sling.apache.org>; Sun, 22 Apr 2012 17:50:31 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r813979 - in /websites/staging/sling/trunk/content: ./
 authentication---actors.html authentication---authenticationhandler.html
 authentication---framework.html authentication---tasks.html
 authentication.html
Date: Sun, 22 Apr 2012 17:50:31 -0000
To: commits@sling.apache.org
From: buildbot@apache.org
X-Mailer: svnmailer-1.0.8-patched
Message-Id: <20120422175031.BF4D823889D5@eris.apache.org>

Author: buildbot
Date: Sun Apr 22 17:50:31 2012
New Revision: 813979

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/authentication---actors.html
    websites/staging/sling/trunk/content/authentication---authenticationhandler.html
    websites/staging/sling/trunk/content/authentication---framework.html
    websites/staging/sling/trunk/content/authentication---tasks.html
    websites/staging/sling/trunk/content/authentication.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Apr 22 17:50:31 2012
@@ -1 +1 @@
-1328916
+1328917

Modified: websites/staging/sling/trunk/content/authentication---actors.html
==============================================================================
--- websites/staging/sling/trunk/content/authentication---actors.html (original)
+++ websites/staging/sling/trunk/content/authentication---actors.html Sun Apr 22 17:50:31 2012
@@ -83,9 +83,6 @@
 
 <p><a name="Authentication-Actors-Actors"></a></p>
 <h1 id="actors">Actors</h1>
-<p>{excerpt}The authentication process involves a number of actors
-contributing to the concepts, the API and the particular
-implementations.{excerpt}</p>
 <p><a name="Authentication-Actors-OSGiHttpServiceSpecification"></a></p>
 <h2 id="osgi-http-service-specification">OSGi Http Service Specification</h2>
 <p>The main support for authentication is defined by the OSGi Http Service

Modified: websites/staging/sling/trunk/content/authentication---authenticationhandler.html
==============================================================================
--- websites/staging/sling/trunk/content/authentication---authenticationhandler.html (original)
+++ websites/staging/sling/trunk/content/authentication---authenticationhandler.html Sun Apr 22 17:50:31 2012
@@ -83,9 +83,6 @@
 
 <p><a name="Authentication-AuthenticationHandler-AuthenticationHandler"></a></p>
 <h1 id="authenticationhandler">AuthenticationHandler</h1>
-<p>{excerpt}The <em>AuthenticationHandler</em> interface defines the service API
-which may be implemented by authentication handlers registered as OSGi
-services.{excerpt}</p>
 <p><em>AuthenticationHandler</em> services have a single required service
 registration property which is used to identify requests to which the
 <em>AuthenticationHandler</em> service is applicable:</p>

Modified: websites/staging/sling/trunk/content/authentication---framework.html
==============================================================================
--- websites/staging/sling/trunk/content/authentication---framework.html (original)
+++ websites/staging/sling/trunk/content/authentication---framework.html Sun Apr 22 17:50:31 2012
@@ -83,10 +83,6 @@
 
 <p><a name="Authentication-Framework-Framework"></a></p>
 <h1 id="framework">Framework</h1>
-<p>{excerpt}The core piece of functionality with respect to authentication in
-Sling is contained in the Sling Commons Auth bundle. This bundle provides
-the API for Sling and Sling applications to make use of
-authentication.{excerpt}</p>
 <p>This support encompasses three parts:</p>
 <ul>
 <li>The <em>AuthenticationSupport</em> service provided by the

Modified: websites/staging/sling/trunk/content/authentication---tasks.html
==============================================================================
--- websites/staging/sling/trunk/content/authentication---tasks.html (original)
+++ websites/staging/sling/trunk/content/authentication---tasks.html Sun Apr 22 17:50:31 2012
@@ -83,10 +83,6 @@
 
 <p><a name="Authentication-Tasks-Tasks"></a></p>
 <h1 id="tasks">Tasks</h1>
-<p>{excerpt}Authentication of HTTP Requests is generally a two-step process:
-First the credentials must be extracted from the request and second the
-credentials must be validated. In the case of Sling this means acquiring a
-JCR Session.{excerpt}</p>
 <p><a name="Authentication-Tasks-ExtractCredentialsfromtheRequest"></a></p>
 <h2 id="extract-credentials-from-the-request">Extract Credentials from the Request</h2>
 <ul>

Modified: websites/staging/sling/trunk/content/authentication.html
==============================================================================
--- websites/staging/sling/trunk/content/authentication.html (original)
+++ websites/staging/sling/trunk/content/authentication.html Sun Apr 22 17:50:31 2012
@@ -83,9 +83,12 @@
 
 <p><a name="Authentication-Authentication"></a></p>
 <h1 id="authentication">Authentication</h1>
-<p>{excerpt:hidden=true}
+<!--
+{excerpt:hidden=true}
 How requests are authenticated.
-{excerpt}</p>
+{excerpt}
+-->
+
 <p>This section describes the framework provided by Sling to authenticate HTTP
 requests.</p>
 <p>Let's look at generic request processing of Sling: Sling is linked into the
@@ -131,25 +134,35 @@ Sling in full detail:</p>
 <li>
 <dl>
 <dt><a href="authentication---tasks.html">Tasks</a></dt>
-<dd>{excerpt-include:Authentication - Tasks|nopanel=true} </dd>
+<dd>Authentication of HTTP Requests is generally a two-step process:
+First the credentials must be extracted from the request and second the
+credentials must be validated. In the case of Sling this means acquiring a
+JCR Session.</dd>
 </dl>
 </li>
 <li>
 <dl>
 <dt><a href="authentication---actors.html">Actors</a></dt>
-<dd>{excerpt-include:Authentication - Actors|nopanel=true} </dd>
+<dd>The authentication process involves a number of actors
+contributing to the concepts, the API and the particular
+implementations.</dd>
 </dl>
 </li>
 <li>
 <dl>
 <dt><a href="authentication---framework.html">Framework</a></dt>
-<dd>{excerpt-include:Authentication - Framework|nopanel=true} </dd>
+<dd>The core piece of functionality with respect to authentication in
+Sling is contained in the Sling Commons Auth bundle. This bundle provides
+the API for Sling and Sling applications to make use of
+authentication.</dd>
 </dl>
 </li>
 <li>
 <dl>
 <dt><a href="authentication---authenticationhandler.html">AuthenticationHandler</a></dt>
-<dd>{excerpt-include:Authentication - AuthenticationHandler|nopanel=true} </dd>
+<dd>The <em>AuthenticationHandler</em> interface defines the service API
+which may be implemented by authentication handlers registered as OSGi
+services.</dd>
 </dl>
 </li>
 </ul>