Martijn C. Vos schrieb:
Apart from your own sitemap.xmap, there's also the cocoon root sitemap
that mounts your sitemap and has some default error handling. It
uses stylesheets/system/error2html.xslt to turn the error message into
the error page you see on your screen.
That is only true if cocoon initializes properly and a subsitemap is
broken. In my case, a classpath in the servlet container leaded to
errors during cocoon initialization. You can produce a similar effect by
renaming a class in cocoon.xconf so that it can't be found (for example
URLSourceFactory). If cocoon.xconf can't be loaded, the sitemap is not
loaded either and you get some kind of standard cocoon page which looks
different than the one used in the root sitemap.
But I think I found a solution in the mid time: in web.xml, change this
setting to false
<init-param>
<param-name>manage-exceptions</param-name>
<param-value>true</param-value>
</init-param>
now the container handles exceptions. I should be able to use standard
web.xml error page configuration now (which of course does only apply
for non handled errors):
Greets,
Nils
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
