Hi Robby,
Here's an example:
<a
href="matchbypath/virtualrootfolder/themes/conservation/index.html">
conservation </a>
=> 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.
Cheers,
Jos
On Thu, May 24, 2012 at 4:38 PM, Robby Pelssers <[email protected]>wrote:
> 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 argument and let
> the generator extract the ids.****
>
> ** **
>
> Robby****
>
> ** **
>
> *From:* Jos Snellings [mailto:[email protected]]
> *Sent:* Thursday, May 24, 2012 4:31 PM
> *To:* [email protected]
> *Subject:* Sitemap: path matching****
>
> ** **
>
> 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?
>
> <map:match pattern="retrievebypath/**/{name}.{extension}">
> <map:generate type="retrieve">
> <map:parameter ?
> </map:generate>
> </map:match>
>
> Of course you could {1}, {2}, {3} .... but that is a clutch.
> Is there an elegant way?
>
> Kind regards,
> Jos
>
>
> --
> The doctrine of human equality reposes on this: that there is no man
> really clever who has not found that he is stupid.
> -- Gilbert K. Chesterson
>
> ****
>
--
The doctrine of human equality reposes on this: that there is no man
really clever who has not found that he is stupid.
-- Gilbert K. Chesterson
