Hi.

I've got a strange problem with the error-page directive and tomcat
5.5.17 + myfaces 1.1 + facelets 1.1.

I have the following in my web.xml:

...
        <!-- error handling -->
        <error-page>
                <exception-type>java.lang.Throwable</exception-type>
                <location>/pages/error.html</location>
        </error-page>
        <error-page>
                <error-code>500</error-code>
                <location>/pages/error.html</location>
        </error-page>   
        <error-page>
                <error-code>404</error-code>
                <location>/pages/error_404.html</location>
        </error-page>
        <error-page>
                <error-code>403</error-code>
                <location>/pages/error_403.html</location>
        </error-page>   
...

If a 403 or 404 error occurs, tomcat perfectly redirects to my custom
pages. But when an error 500 occurs (e.g. a provoked
NullpointerException) it displays the std. tomcat error page. There's
nothing in the logs about a faulty error.html nor any error on startup.
I also replace error.html with error_404.html just to make sure, it
isn't problem with the error.html content. Any hints, what this can be?
It turned on debugging in tomcat - but there's nothing logged about the
web.xml/error-page parsing. Any ideas how to come closer to the problem?

regards,
Veit




---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to