Oh sorry, I want to use the parameters during stylesheet generation.
My stylesheet is a xsp-page looking for some request parameters and
session variables to get the colors customized by the user from the
database.
So, the stylesheet is dynamicly generated depending on the request.
But I had the problem that the request Variable doesn't contain
the parameters!
I had the same problem during using aggregate, the request is not available
in the part generators.
Is it my mistake or not the way cocoon works?
(I need the current request in every phase of generation, i thought that is
for
what the cocoon:// protocol is for!?)
Christoph Gaffga
----- Original Message -----
From: "Sergio Carvalho" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 13, 2001 7:34 PM
Subject: Re: [C2] use-request-parameters=true
>
> Do you want to use the request parameter *in* the XSLT or *producing* the
XSLT? You mentioned using it in the XSLT but your sample uses it in XSP
instead.
>
> You sample should work, even without the <map:parameter
name="use-request-parameters" value="true"/>.
>
> On the other hand, if you want to use the parameters in the XSLT, then
what you need to do is this:
> 1) Edit sitemap.xmap; change
>
> <map:transformer name="xslt"
src="org.apache.cocoon.transformation.TraxTransformer">
> <use-store>false</use-store>
> <use-request-parameters>true</use-request-parameters>
>
> to
>
> <map:transformer name="xslt"
src="org.apache.cocoon.transformation.TraxTransformer">
> <use-store>true</use-store>
> <use-request-parameters>true</use-request-parameters>
>
> 2) Declare the parameter in your XSLT. e.g:
>
> <xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
> <xsl:param name="siteSection">/</xsl:param>
>
> 3) Use the parameter, available as $siteSection in the example. e.g:
>
> <xsl:when test="$siteSection = '/frontPage'">
>
> Hope this helps,
>
> On Fri, 13 Jul 2001 15:24:12 +0200, "C. Gaffga" <[EMAIL PROTECTED]>
wrote:
> --
> > I'm using cocoon 2.1-dev (12.07.2001).
> > I want to use the request in a dynamic generated Stylesheet using the
> > following sitemap:
> >
> > <map:match pattern="test.xsl">
> > <map:generate type="serverpages" src="stylesheet.xsp"/>
> > <map:serialize type="xml"/>
> > </map:match>
> >
> > <map:match pattern="test.html">
> > <map:generate type="serverpages" src="page.xsp"/>
> > <map:transform src="cocoon://test.xsl">
> > <map:parameter name="use-request-parameters" value="true"/>
> > </map:transform>
> > <map:serialize type="html"/>
> > </map:match>
> >
> > I have the following im my stylesheet.xsp for testing:
> >
> > Request Parameter:
> > <ul><xsp:logic>
> > {
> > java.util.Enumeration x = request.getParameterNames();
> > while(x.hasMoreElements()) {
> > String s = (String) x.nextElement();
> > <xsp:content>
> > <li><xsp:expr>s</xsp:expr> =
> > <xsp:expr>request.getParameter(s)</xsp:expr></li>
> > </xsp:content>
> > }
> > }
> > </xsp:logic></ul>
> >
> > But there are no parameters outputted! Is it a bug or my mistake?
> > Please help.
> >
> > Christoph Gaffga
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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]>
> >
>
>
>
> --
> Sergio Carvalho
> ---------------
> [EMAIL PROTECTED]
>
> If at first you don't succeed, skydiving is not for you
>
> ---------------------------------------------------------------------
> 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]>
