Thank you! That did it.
--
Tom
Igor Vaynberg wrote:
i think in the filter mapping you will need to add
<dispatcher>REQUEST</dispatcher>
<dispatcher>ERROR</dispatcher>
-igor
On Tue, Jul 1, 2008 at 11:17 PM, Thomas Singer <[EMAIL PROTECTED]> wrote:
I'm using Tomcat 5.5.26 with Wicket 1.3.4 and try to show an own error page
when an invalid URL is requested. I've added following lines at the end of
our web.xml:
<error-page>
<error-code>404</error-code>
<location>/404.html</location>
</error-page>
and mapped a wicket page to the path /404.html. The page displays correctly
when I enter http://server/404.html in the browser, but it fails for its
purpose by entering any non existing URL.
We are also using the WicketSessionFilter as well as own filters. But when
debugging, the invalid URL is passed through our own filter as well as
through the WicketFilter (chain.doFilter(request, response) is called in
both cases.
Does somebody have an idea why the error page fails to display?
--
Thanks in advance,
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
