That won't solve Jos's issue I'm afraid. From the docs it states: 'If set to
true the values of a request parameter is available using a variable in the
xslt with the name of the parameter.' Jos doesn’t know which parameters will
be passed upfront. This is merely a shortcut that prevents you fr
Hello Gilbert,
A way to catch multiple parameter is to have your own stylesheet where you
define as many parameters as you need and then you use the XSLT
Transformer[1] to get them on your pipeline.
The way to retrieve your parameters is setting to "true" the property
"use-request-parameters" at
Yep, I will give that a try !
Thanks, Robby,
Jos
But as a little side note:
If all files in these folders were treated uniformely.. let's say with a
map:read
You could just as well do
From: Robby Pelssers [mailto:robby.pelss...@nxp.com]
Sent: Thursday, May 24, 2012 4:48 PM
To: users@cocoon.apache.org
Subject: RE: Sitemap: path matching
The only way to work around this is what I've used in the past.
matchbypath/index.html/virtualrootfolder/themes/conservation
pattern="matchbypath/*.*/**"
From: Jos Snellings [mailto:jos.snelli...@upperware.biz]
Sent: Thursday, May 24, 2012 4:45 PM
To: users@cocoon.apache.org
Subject: Re: Sitema
Hi Robby,
Here's an example:
conservation
=> this is to be a hit for a matcher, and what I would like
to pass to the generator:
"matchbypath/{path}/{name}.{extension}"
Of course, the pipeline matcher cannot know how many segments
there will be.
Can you give a few possible examples of the pattern that you're trying to match?
Ps. Maybe a bit nasty as solution but let's say you want to handle multiple
productId's
Pattern="generateProduct/*"
Example
generateProduct/[P1, P2, P3]
You just pass '[P1,P2,P3]' to your generator as a single
Hi all,
I am looking for a way to pass a variable number of sitemap parameters to a
sitemap component:
I explain the use case:
"**" stands for non-greedy multiple segment matcher, no?
Of course you could {1}, {2}, {3} but that is a clutch.
Is there an elegant way?
Ki
