Btw, this is what you want: http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/request/cycle/AbstractRequestCycleListener.html#onException%28org.apache.wicket.request.cycle.RequestCycle,%20java.lang.Exception%29
Add your own IRequestCycleListener (AbstractRequestCycleListener) with org.apache.wicket.Application.getRequestCycleListeners().add() and implement its #onException(RequestCycle, Exception) then drop that in your HTML comment. On Wed, Jun 4, 2014 at 11:31 AM, Paul Bors <p...@bors.ws> wrote: > Why? You don't have access to your own log file? > > > On Wed, Jun 4, 2014 at 10:43 AM, Entropy <blmulholl...@gmail.com> wrote: > >> We set our error page via setInternalErrorPage on IApplicationSettings in >> 1.6. I'd like to bury the stack trace in a comment in the rendered page >> in >> our staging and dev environments to save time. But I have no idea how to >> get the originating trace in the error page. >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Error-page-stack-trace-tp4666119.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >
