I think I have found the problem.
Should be better with the fix in
https://issues.apache.org/jira/browse/WICKET-4722
On Fri, Aug 10, 2012 at 2:53 PM, Martin Grigorov wrote:
> No, these are no errors.
> These are kept only in case of error.
> We can improve though by removing them in Component#det
No, these are no errors.
These are kept only in case of error.
We can improve though by removing them in Component#detach(). I see no
reason to keep them around after the first render of the page.
Please file a ticket.
On Fri, Aug 10, 2012 at 2:45 PM, Andrew Geery wrote:
> I'm using Wicket 1.5.7.
I'm using Wicket 1.5.7. I understand how to turn the stacktraces on and
off (in development more I have both those settings turned on). My
question is more: the files look like they are indicating an error is
happening, but I don't get a stacktrace at run-time. For example, if I
have a mismatch
Hi,
Which version of Wicket do you use ?
See
org.apache.wicket.settings.IDebugSettings#setLinePreciseReportingOnAddComponentEnabled
and
org.apache.wicket.settings.IDebugSettings#setLinePreciseReportingOnNewComponentEnabled.
When set to true these create an exception and saves its stacktrace as
