Hi,

"portal-adminconf" and "portal-sunriseconf" both contain this action in
their pipeline:

                        <map:act type="sunSpot-auth">
                            <map:parameter name="sunLet"
value="administration"/>
                        </map:act>

By using this action, both documents are only accessible if the user is
allowed
to see/select the "administration" sunLet, so usually this is the
administrator.
I guess you are not logged in as an administrator but as a user.

So these two documents are double-protected, once with the sunRise handler
and
second with the sunSpot sunLet mechanism.

HTH
Carsten

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, March 31, 2002 1:28 AM
> To: [EMAIL PROTECTED]
> Subject: [SunRise] sunriseconf/adminconf in sitemap
>
>
> Hey folks,
>
>   I'm working on getting a site going with the sunRise components and I am
>   currently having a probelm getting sunSpot-conf and sunRise-conf working
>   or even clearly not working. Whenever I go to the respective
> pages, I get
>   a Tomcat 404 error.
>
>   I have the generators mapped, and the following in the pipeline:
>
>             <map:match pattern="**">
>                 <map:act type="sunRise-auth">
>                     <map:parameter name="handler"
> value="fpiDataPortalHandler"/>
>                     <map:parameter name="application" value="portal"/>
> <!-- snip -->
>                     <map:match pattern="portal-conf">
>                         <map:generate type="sunSpot-conf"/>
>                         <map:transform src="stylesheets/blank.xsl"/>
>                         <map:transform type="encodeURL"/>
>                         <map:serialize/>
>                     </map:match>
>                     <!-- Admins only -->
>                     <map:match pattern="portal-adminconf">
>                         <map:act type="sunSpot-auth">
>                             <map:parameter name="sunLet"
> value="administration"/>
>                         </map:act>
>                         <map:generate src="admin" type="sunSpot-conf"/>
> <!-- blank.xsl simply copies the incoming XML and sends it to the
> browser (in hopes that reading the XML will teach me something
> about sunRise)-->
>                         <map:transform src="stylesheets/blank.xsl"/>
>                         <map:transform type="encodeURL"/>
>                         <map:serialize/>
>                     </map:match>
>                     <!-- Admins only -->
>                     <map:match pattern="portal-sunriseconf">
>                         <map:act type="sunSpot-auth">
>                             <map:parameter name="sunLet"
> value="administration"/>
>                         </map:act>
>                         <map:generate type="sunRise-conf"/>
>                         <map:transform src="stylesheets/blank.xsl"/>
>                         <map:transform type="encodeURL"/>
>                         <map:serialize/>
>                     </map:match>
>
> I can get to "portal-conf" just fine (though I have some
> questions about that I'll ask later), but I have no idea why
> portal-adminconf and portal-sunriseconf come up as 404.  As you
> may have guessed, this is my first run with Cocoon so idiotic
> mistakes are quite likely the source of my angst.
>
> Cocoon - 2.0.2
> Tomcat - 4.0.3-LE
> JDK - 1.3.1
> OS = Linux && NT
>
>
> --
> --
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Reply via email to