Re: [Wicket-user] Proxessing uncaught exceptions

2006-07-12 Thread Tymur Porkuyan
> If you want to get hold on the actual exception that has been thrown you > need to override the ExceptionResponseStrategy in > DefaultWebRequestCycleProcessor. Thanks, it's exactly what I wanted :) - Using Tomcat but need

Re: [Wicket-user] Proxessing uncaught exceptions

2006-07-11 Thread Igor Vaynberg
or simply override requestcycle.onruntimeexception-IgorOn 7/11/06, Frank Bille Jensen <[EMAIL PROTECTED] > wrote:If you want to get hold on the actual exception that has been thrown you need to override the ExceptionResponseStrategy inDefaultWebRequestCycleProcessor. Do something like this:In you W

Re: [Wicket-user] Proxessing uncaught exceptions

2006-07-11 Thread Frank Bille Jensen
If you want to get hold on the actual exception that has been thrown you need to override the ExceptionResponseStrategy in DefaultWebRequestCycleProcessor. Do something like this: In you WebApplication extended class: @Override protected IRequestCycleProcessor newRequestCycleProcessor() {

Re: [Wicket-user] Proxessing uncaught exceptions

2006-07-11 Thread Frank Bille Jensen
Yes, take a look at IApplicationSettings.setInternalErrorPage(). Frank Bille On Tue, 2006-07-11 at 09:46 +0300, Tymur Porkuyan wrote: > Is it possible to override standard Wicket exception page? > > I would like to throw exceptions on lower levels and have a generic > error page that will dis