Okay, still missing something basic.
I was looking at the Library in wicket-examples, and it failed. (I have
no idea why, and am downloading the lastest beta of examples.) But when
it failed -- after log-in -- Wicket presented me with a nicely formatted
error report listing the stack-trace,
so you always get a internal one?
that is strange because if you are in development mode:
if (development.equalsIgnoreCase(configurationType))
{
setResourcePollFrequency(Duration.ONE_SECOND);
setComponentUseCheck(true);
setStripWicketTags(false);
Isn't it possible that this is due to the web.xml url pattern '/'
instead of '/*' ?
Martijn
Johan Compagner wrote:
so you always get a internal one?
that is strange because if you are in development mode:
if (development.equalsIgnoreCase(configurationType))
{
Johan Compagner wrote:
so you always get a internal one?
that is strange because if you are in development mode:
if (development.equalsIgnoreCase(configurationType))
{
setResourcePollFrequency(Duration.ONE_SECOND);
setComponentUseCheck(true);
My web.xml contains this:
.url-pattern/admin/*./url-pattern
Every time I've tried to use /* I ended up with some problem. I've
never had the time to spend trying to figure out why, but maybe I should.
-- Scott
Martijn Dashorst wrote:
Isn't it possible that this is due to the
or the exception page is erroring itself..
You could try to debug it start in RequestCycle.internalOnRuntimeException()
johan
Scott Sauyet wrote:
Johan Compagner wrote:
so you always get a internal one?
that is strange because if you are in development mode:
if
