cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ovidiu Predescu <>
Subject Re: defaulting to a matcher when another one is not present
Date Tue, 08 Oct 2002 03:01:58 GMT

On Monday, October 7, 2002, at 05:27  AM, Christian Haul wrote:

> On 06.Oct.2002 -- 10:28 AM, Sylvain Wallez wrote:
>> Ovidiu Predescu wrote:
>>> I have the following problem. I want to write a <map:match
>>> pattern="**.html"> matcher in the top-level sitemap, and have it
>>> invoked for most of the HTML page generation. However I'd like this
>>> rule to be overwritten in sub-sitemaps, e.g. if a sub-sitemap
>>> implements a  rule with a similar pattern, this rule should take
>>> precendence. This would be very similar to the precedence rule in
>>> XSLT, allowing developers to define catch-all rules, while still
>>> permitting the rule to be rewritten.
>>> Do we have something like this which can implement this behavior?
>> What if we could "come back" from a <map:mount> to the parent sitemap 
>> if
>> no pattern matched in the subsitemap ?
> Could you do a
> <map:match pattern="*">
>   <map:redirect-to uri="../not-found"/>
> </map:match>
> or something as last one and cascade the way up?

This should work as well, except that it makes another round-trip to 
the client browser: ugly!


To unsubscribe, e-mail:
For additional commands, email:

View raw message