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 String in the Component's meta data. This stacktrace is used to find when and where the problem happened. These stacktraces are printed only if org.apache.wicket.settings.IDebugSettings#getComponentUseCheck() returns true. On Fri, Aug 10, 2012 at 4:16 AM, Andrew Geery <[email protected]> wrote: > I have a question about why I am seeing stack traces in my wicket-filestore > files. This question has been asked before ( > http://apache-wicket.1842946.n4.nabble.com/Strange-content-serialized-td1933194.html), > but I don't understand the answer. When I run the app, I don't get any > errors -- all of the components render fine. However, in the files I see > errors like this: > > The webmarkupcontainer with id 'content' that failed to render was added > > In the previous thread, the answer was that the error was there because > there was a discrepancy between the Java hierarchy and the HTML file. > However, if there was an error, wouldn't I get a run-time error (since I > am running the app in development mode)? Why, when there isn't > a discrepancy, is there a stack trace in the cache? > > Thanks > Andrew -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
