Well, maybe what I supposed to know about pipelines and matchers is wrong, but ... <map:match pattern="mysite/**"> <map:mount check-reload="yes" reload-method="synchron" src="mysite/sitemap.xmap" uri-prefix="mysite"/> </map:match> and the mounted pipeline is something like: <map:match pattern="index.html"> <map:read src="index.html"/> </map:match> <map:match pattern="dir1/dir2/index.html"> <map:read src="index.html"/> </map:match> <map:handle-errors> <map:transform src="error.xsl"/> <map:serialize type="html"/> </map:handle-errors> Now, if I call http://localhost:8080/cocoon/mysite/index.html or http://localhost:8080/cocoon/mysite/dir1/dir2/index.html it works but if I try http://localhost;8080/cocoon/mysite/anything.html I get the well known white page with the blu header "Cocoon 2 - Resource not found", while I expected to find my custom error page. Coccon processes a request which begins with "mysite" and, according to the "2 asterisks rule", the mounted pipeline is executed. But there isn't a pattern that matches the request, an error occurs. So why my custom handler isn't processed? Where I'm wrong? Cocoon 2.0.3 - Tomcat 4.1.12 - j2sdk1.4.0 - Win2k server ----------------------------------------------------------------------- > Nice guess, but three asterisks is not defined. mysite/** will match > literally everything after the slash. If you need to seperate out the file > extension, you can do mysite/**.* (the values will be stored in {1} an d {2}) > but then you have to have a .XXX request. If you will only sometimes have a > .XXX match, you need to either split the pipeline into two different o nes, > or use a regexp matcher (which may not be defined in the default sitem ap). > > Geoff Howard >
--------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>