And why map:call cannot forward to another matcher?
You can nest matchers, redirect external or internal ("cocoon:" protocol). There are resources. And in the future, arbitrary pipeline fragments. BTW map:call does expand sitemap variables.
In fact I want to do it really clean, I have one general matcher: <map:match pattern="*_*">
Wouldn't it be cleaner to have different pipelines than to mix them?
which handles over 50 pages. 6 of them I have to do through request param selector - of course I could copy the content of that general matcher in every map:when place, but it is not the right way of programming :(
So, why don't you put the common stuff into a resource?
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
