Wicketeers,
I have another hard-to-track down issue.
To make matters worse, I've actually taken this code/pattern, put it into a
quickstart - and what do you know - it works fine...! This means I have no way
to recreate this error in a demonstrable way. Hopefully if I throw this out
there,
Hi,
I am an expert in shooting myself in the foot with Wicket / Java
problems.
In a situation like this, I would do the same as you do - isolate the
pattern and make a quickstart. Unfortunately, this approach is full of
assumptions, and my statistics say that this succeeds only in 20% of
all
Yeah, I know exactly what you mean - I'm sure it's something I'm doing! :)
I might have to do as you suggest... I was just hoping for a 'you'd only get
this error if you'd done something stupid like' and give me something to go
on! ;)
Cheers,
Col.
-Original Message-
From: Bernard
Hello,
my application runs in deployment-mode and if an exception is thrown, wicket
shows his internal error page without the stacktrace. Is there any possibility
to show this stacktrace in this wicket error page? How can I get the stacktrace
of an exception to show it in a custom error page?
