cvs commit: xml-cocoon2/src/documentation/xdocs/developing portal.xml

[cziegeler]

cziegeler    02/05/06 01:41:00

  Modified:    src/documentation/xdocs/developing portal.xml
  Log:
  Clarified the docs a little bit
  
  Revision  Changes    Path
  1.2       +20 -3     xml-cocoon2/src/documentation/xdocs/developing/portal.xml
  
  Index: portal.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/developing/portal.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- portal.xml        23 Apr 2002 10:25:32 -0000      1.1
  +++ portal.xml        6 May 2002 08:41:00 -0000       1.2
  @@ -1067,9 +1067,26 @@
        <s2 title="Defining coplets">
           <p>Defining a pipeline for a coplet is also very straightforward.
             Together with your "real" pipeline for defining the content and doing the
  -          presentation, the "portal-auth" action and the auth-protect action are 
needed.
  -          The first one for protecting the coplet and the second one for defining 
the
  -          application the resource belongs to:</p>
  +          presentation, the "auth-protect" action is needed. This action defines
  +          the application and portal, the coplet (pipeline) belongs to:</p>
  +        <source>             &lt;map:match pattern="licence-coplet"&gt;
  +      &lt;!-- Get the application configuration --&gt;
  +                  &lt;map:act type="auth-protect"&gt;
  +                         &lt;map:parameter name="handler" value="portalhandler"/&gt;
  +                         &lt;map:parameter name="application" value="sunBank"/&gt;
  +
  +                &lt;!-- The resource containg the licencing information: --&gt;
  +          &lt;map:generate src="cocoon/licencing.xml"/&gt;
  +
  +          &lt;!-- present it in HTML --&gt;
  +                      &lt;map:transform src="sunbank/styles/HTML.xsl"/&gt;
  +          &lt;!-- Serialize it to XML for including in the portal view: --&gt;
  +                      &lt;map:serialize/&gt;
  +      &lt;/map:act&gt;
  +        &lt;/map:match&gt;</source>
  +        <p>In addition you can secure the pipeline of the coplet. So only users
  +           who can select this coplet in their profile can invoke the pipeline.
  +           This extra protection is performed by the "portal-auth" action:</p>
           <source>             &lt;map:match pattern="licence-coplet"&gt;
         &lt;!-- Get the application configuration --&gt;
                     &lt;map:act type="auth-protect"&gt;
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     [EMAIL PROTECTED]
To unsubscribe, e-mail:          [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]