cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gell, Ashley" <>
Subject RE: outputing parameters in XSP
Date Tue, 07 Oct 2003 13:28:40 GMT
I am using Cocoon 2.1.1

As illustrated by the sample pipeline below, I have a navigate action which
determines, among other things, the buttons to be displayed on the page.
The current page is passed into the navigate action, which is used to
determine and return the buttons parameter to the pipeline indicating which
buttons xsl to apply.

I now have a requirement that, depending on the result of a
'createService.xsp' (running <map:generate type="serverpages"
src="{../1}/xsp/{../2}.xsp"/>) different buttons to those returned by the
navigate action need to be displayed.  This could be achieved, I am hoping,
by the XSP over writing the 'buttons' parameter returned by the navigate
action by returning the 'buttons' parameter itself.

Any ideas?
<map:match pattern="*/*.xsp">
   <map:act type="xsp-action" src="{1}/xsp-action/navigate.xsp">
      <map:parameter name="currPage" value="{2}.xsp"/>
      <map:generate type="serverpages" src="{../1}/xsp/{../2}.xsp"/>
      <map:transform type="xslt" src="{../1}/style/{../2}.xsl"/>
      <map:transform type="xslt" src="common/style/{buttons}.xsl"/>
    <map:generate type="serverpages" src="common/xsp/invalidpage.xsp"/>
    <map:transform type="xslt" src="common/style/invalidpage.xsl"/>
    <map:transform type="xslt" src="common/style/pagestyle.xsl"/>


-----Original Message-----
From: Geoff Howard []
Sent: Tuesday, October 07, 2003 1:08 PM
Subject: Re: outputing parameters in XSP

Gell, Ashley wrote:
> Sitemap parameters can be passed into an XSP but how do you set and pass 
> out parameters to the pipeline from the XSP.  I have found the utility 
> tag <xsp-util:get-sitemap-parameter/> but can't seem to find an 
> equivalent <xsp-util:get-sitemap-parameter/> tag.
> I need to be able to set a parameter within an XSP and have it visible 
> by the pipeline.

What you are using it for makes a big difference.  Can you give a basic 
idea of your use case?  If you are trying to dynamically affect the 
course of a pipeline after it begins (after your xsp starts executing) 
you'll need to refactor your strategy as that is disallowed in Cocoon.

We'll also need to know what version of Cocoon you're using.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message