That's what we suspected. So we stick with our workaround.
Thanks
Pedro Santos escribió:
The init method is called by the wicket servlet filter. If it throw an
exception the web container will not place the filter into service, than the
request will not be handled by wicket.
On Fri, Oct 23, 2009 at 3:26 PM, Josh Glassman <[email protected]> wrote:
There is a wiki page with information on creating custom error pages.
http://cwiki.apache.org/WICKET/error-pages-and-feedback-messages.html
Hopefully that is what you are looking for!
Josh
On Fri, Oct 23, 2009 at 12:34 PM, Tomás Rossi <[email protected]> wrote:
Hey people,
I've noted that if an exception occurs during the execution of init
method
of MyApplication (which extends WebApplication), a SERVICE UNAVAILABLE
(error 503) page shows. We'd like to have our own error page for this
case
and figured out a workaround which includes catching and saving the
exception in the init method, setting some state and then handling it
later...
But, what is the Wicket way of doing this?
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]
