Ok ill stay with what I have then because it will work when you enhance your respond method :)
I do not think being able to skin or extend the ExceptionErrorPage is "so custom" as to be unsupported, but I do have an ugly solution that works around this shortcoming. Rgds Ned igor.vaynberg wrote: > > sounds to me like what you should do is simply subclass > webrequestcycleprocessor and override the entire > respondonruntimeexception() and ignore whatever is in the app > settings. simply return your own page that would inspect the user and > based on that display the general message and maybe the stacktrace if > appropriate. it can also take the applicaton's deployment mode if you > want. > > sounds to me like what you want is so custom there is no positive > reason to reuse what is already there. > > -igor > -- View this message in context: http://www.nabble.com/Can-we-expose-ExceptionErrorPage-via-IApplicationSettings-please-%21-tp16758488p16760381.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]
