Hi,
just for your information: today I noticed, when upgrading a site to
hippo-cocoon-2.1.11, that pipeline pattern matching behaviour has
changed. The problem I had occurred when using "capture variables" (or
whatever they're called) within a pipeline, like {1}, {2}, etc. My old
pipeline matcher was:
<map:match pattern="get*/*|**">
, and when the pipeline is called with the url "getFoo/Bar||/some/url",
then in previous versions of Cocoon (< 2.1.11), {2} would evaluate to
"Bar", but in Cocoon 2.1.11, it evaluates to "Bar|", which broke the
functionality of that pipeline. So it seems that the value that is
"captured" is captured in a "wider" fashion than before. Something to
consider when you're upgrading to hippo-cocoon-2.11.xx using weirdo
patterns like me!! :)
In my case I fixed it by making the pattern more specific:
<map:match pattern="get*/*|**|**">
and then {2} will evaluate to "Bar" in the example.
regards,
Dennis
--
Hippo
[EMAIL PROTECTED]
Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1 (707) 773-4646
www.onehippo.com [EMAIL PROTECTED]
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
