From: gounis > now i > 1. produce a xml with the request parameters using .xsp > 2. aggregate this with the .xml i want to transform > 3. transform all this with a .xsl > > but will be cleaner to have a simple .xml/xsl transformation > passing the > request parameters as parameters in sitemap > > .. the action sounds pretty good but if something allready exist ?
... if InputModules don't work in 2.0.4 (I don't know) use the org.apache.cocoon.acting.RequestParamAction. Reinhard > > > On Wed, 22 Oct 2003, Reinhard Poetz wrote: > > > I also think that input modules work in 2.0.4 but if not > > you can either use an XSP page to get the request parameter > > our you can write an action that reads the param and pass > > it to the transformer in the pipeline. > > > > Reinhard > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, October 22, 2003 9:09 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: cocoon 2.0 - catch a request parameter in sitemap > > > > > > > > > > > > BUT i have to do this in 2.0.4 ??? > > > > > > On Wed, 22 Oct 2003, Tony Collen wrote: > > > > > > > [EMAIL PROTECTED] wrote: > > > > > hi > > > > > > > > > > i try to catch a request parameter inside the sitemap and > > > sent it as > > > > > parameter in a xslt transformation > > > > > > > > > > something like > > > > > > > > > > <map:transform src="stylesheets/my.xsl"> > > > > > <map:parameter name="your-parameter-name" > > > > > value="{request-param:my-parameter-value}"/> > > > > > </map:transform> > > > > > > > > > > but in cocoon 2.0.4 > > > > > > > > > > is it possible or ia have to use .xsp to catch the > parameter and > > > > > then > > > > > transform the xml that this xsp generate ? > > > > > > > > Yes, see > > > http://cocoon.apache.org/2.1/userdocs/c> oncepts/modules.html, > > > > > > > which describes how to use > > > > input > > > modules with XSP pages. > > > > > > > > > > > > Regards, > > > > > > > > Tony > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
