cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tcu...@dff.st
Subject Re: defaulting to a matcher when another one is not present
Date Wed, 09 Oct 2002 14:31:36 GMT
Quoting Vadim Gritsenko <vadim.gritsenko@verizon.net>:

> tcurdt@dff.st wrote:
> 
> >>>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!
> >>    
> >>
> >
> >you could also use a resource - then it should be an internal redirect...
> >
> >btw: do we already have an "always" matcher?
> >due to the lastest performance analysis we should better
> >substitute
> >
> ><map:match pattern="*"> or <map:match pattern="**">
> >
> >with 
> >
> ><map:match type="always">
> >
> >or similiar...
> >
> 
> You can always omit "always" match - absence of match also always matches
> :)
> 

You mean a <map:generate/> etc. directly in <map:pipeline/>??

Everyday you learn something new... :)
--
Torsten

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message