OK, some sloppy copying as well!
Originally, this would look like:
>
> >
> >
> >
So besides the request-parameters a paramater named path is also passed to the xsl,
which can be helpfull. For instance, you're building a navigation, then the xml and
xsl would be the same for
Rogier Peters wrote:
> the trick you're looking for is:
>
>
>
>
> The parameter use-request-paramaters will (almost) automatically make the request
>parameters available as normal xsl:parameters. Almost, because you then have to
>define those parameters in your xsl (of course)
Thanks a lot for your help.
I finally managed it with the use of an xalan:evaluate($q) inside the
select !
And it works, if you declare the xalan namespace !
I will keep in mind the trick of the "cocoon:/myStylesheet.xsl" to call a
pipeline from inside an other !
Guy Bobenrieth
--
> From: GB [mailto:[EMAIL PROTECTED]]
>
> Dear Cocoon readers !
>
> I need to transform a xslt stylesheet before using it over an
> xml file.
>
> In fact, what I want to do is to modify the stylesheet so
> that a parameter,
> taken out of the http request, could be used as an xpath
> string
I think Xalan has an evaluate() function that allows dynamic
constraction of an Xpath expression.
Hth,
Manos
> -Original Message-
> From: GB [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 18, 2002 3:26 PM
> To: [EMAIL PROTECTED]
> Subject: Modifying an xslt stylesheet before utilisa
Sorry, fired that one off too fast, did'nt read the problem thoroughly
>
> the trick you're looking for is:
>
>
>
>
> The parameter use-request-paramaters will (almost)
> automatically make the request parameters available as normal
> xsl:parameters. Almost, because you then hav
the trick you're looking for is:
The parameter use-request-paramaters will (almost) automatically make the request
parameters available as normal xsl:parameters. Almost, because you then have to define
those parameters in your xsl (of course)
With kind regards / Met vriendel