It depends on the deployment setting what you will see. Take a look at the wicket in action examples (http://wicketinaction.googlecode.com), currently chapter 15 (soon to become chapter 14).
Martijn On 2/18/08, Doug Leeper <[EMAIL PROTECTED]> wrote: > > I would like to display a common error page when ever there is a problem (aka > RuntimeException) in a Page's constructor. I thought by calling > getApplicationSettings().setInternalErrorPage(ErrorPage.class); in the > Application.init class would do the trick...but that is not the case. > > Our scenario is that we encountered a NPE during a Page's constructor. The > page displayed showed "Unexpected Runtime Exception" with the stack trace. > We want to handle this gracefully (send an email to support) and "nicer > looking" (same Look and Feel as our site). > > What am I missing? or what do I need to do? > > Thanks in advance, > - Doug > -- > View this message in context: > http://www.nabble.com/Error-handling-for-RuntimeExceptions-during-page-construction-tp15547476p15547476.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.1 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.1 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
