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 On Thu, Apr 17, 2008 at 8:47 PM, Ned Collyer <[EMAIL PROTECTED]> wrote: > > My customers can be a middle man developer - consuming my product as > developers - these guys should see the strack trace - but it should be nice > and blue, have my headers, and some of my behaviour in it :) > > I'd like to be able to style and customise exceptions on a page that has > scope to the exceptions AND use the settings exposed thru the > IApplicationSettings interface (ie, set error pages, page expired etc). > > Maybe I turn it on in production, but you only get the full stack trace if > you have a certain permission (ie, Role = admin). > > Again, I'm unsure this is not exposed. > > > > igor.vaynberg wrote: > > > > because one page is meant for production use and another for > > development. you dont want your end customers seeing your stacktrace > > do you? > > > > -igor > > > > -- > View this message in context: > http://www.nabble.com/Can-we-expose-ExceptionErrorPage-via-IApplicationSettings-please-%21-tp16758488p16760013.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
