On Wed, Jun 4, 2014 at 5:34 PM, Sven Meier <s...@meiers.net> wrote: > Hi, > > easiest solution is to use a custom requestCycleListener to store the > exception in a thread-local. > You can access this variable from your custom internalErrorPage. >
Prefer RequestCycle's metadata instead. > > Hope this helps > Sven > > > > On 06/04/2014 04:43 PM, Entropy 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 >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
