hortcut that prevents you from typing all
parameters as
Robby
-Original Message-
From: ktor...@agssa.net [mailto:ktor...@agssa.net]
Sent: Thursday, May 24, 2012 6:55 PM
To: users@cocoon.apache.org
Cc: cocoon-us...@apache.org
Subject: Re: Sitemap: path matching
Hello Gilbert,
A way to
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 mat
org
Subject: Re: Sitemap: path matching
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 pipe
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
