Return-Path: Delivered-To: apmail-cocoon-cvs-archive@www.apache.org Received: (qmail 19350 invoked from network); 18 Nov 2005 04:26:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Nov 2005 04:26:36 -0000 Received: (qmail 24236 invoked by uid 500); 18 Nov 2005 04:20:42 -0000 Delivered-To: apmail-cocoon-cvs-archive@cocoon.apache.org Received: (qmail 19728 invoked by uid 500); 18 Nov 2005 04:17:45 -0000 Mailing-List: contact cvs-help@cocoon.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@cocoon.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list cvs@cocoon.apache.org Received: (qmail 18486 invoked by uid 99); 18 Nov 2005 04:16:58 -0000 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 17 Nov 2005 20:15:21 -0800 Received: (qmail 7405 invoked by uid 65534); 18 Nov 2005 04:15:00 -0000 Message-ID: <20051118041500.7404.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r345438 [31/286] - in /cocoon/site/site/2.1: ./ developing/ developing/portal/ developing/portal/coplets/ developing/webapps/ developing/webapps/authentication/ faq/ howto/ installing/ plan/ plan/documentation/ plan/otherplanning/ plan/over... Date: Fri, 18 Nov 2005 04:13:22 -0000 To: cvs@cocoon.apache.org From: crossley@apache.org X-Mailer: svnmailer-1.0.5 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Added: cocoon/site/site/2.1/developing/webapps/authentication/module_management.html URL: http://svn.apache.org/viewcvs/cocoon/site/site/2.1/developing/webapps/authentication/module_management.html?rev=345438&view=auto ============================================================================== --- cocoon/site/site/2.1/developing/webapps/authentication/module_management.html (added) +++ cocoon/site/site/2.1/developing/webapps/authentication/module_management.html Thu Nov 17 20:00:02 2005 @@ -0,0 +1,1288 @@ + + + + + + + +Authentication Framework: Module Management + + + + + + + + + +
+ + + +
+ + + + + + + + + + + + +
+
+
+
+ +
+ + +
+ +
+ +   +
+ + + + + +
+

Authentication Framework: Module Management

+ +

+
+

In addition to the application management feature, the framework offers a +facility called module management. It enhances the application management by +adding the possibility of configuring components for the application. For +example, the Cocoon portal engine needs information about the source of the +portal profile for the user, about where the layout is stored, etc. Each portal +needs this information. Assuming that a portal is an application each +application needs this information. As only the portal engine itself knows what +information it needs, the module management is a standarized way for configuring +such components.

+

The module configuration is part of the application configuration:

+
<autentication-manager>
+  <handlers>
+    <handler name="unique">
+      ....redirect-to/authentication configuration
+      <applications>  <!-- the applications for this handler -->
+        <application name="unique">
+          ...
+          <configuration name="portal">
+            ...portal configuration
+          </configuration>
+        </application>
+      </applications>
+    </handler>
+  </handlers>
+</autentication-manager>
+

So whenever the portal engine is asked to build the portal it can easily +retrieve its configuration from the current application by getting the module +configuration named "portal".

+ +
+
+ +
 
+
+ + + Propchange: cocoon/site/site/2.1/developing/webapps/authentication/module_management.html ------------------------------------------------------------------------------ svn:eol-style = native