Currently within webwork2, a html page is generated. I suggest that if an action throws an exception, a http server error - code 500 - page is provided, then using the standard servlet mapping in web.xml, the developer can map this to a custom error page and display whatever they want. I have implemented this patch in my workspace, and can commit it to the repository if this is what people want.
Another idea (ww2 specific) is to create an exception handling interceptor, and dispatch to a relevant view. Cameron > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Francisco Hernandez > Sent: Sunday, 20 July 2003 9:10 AM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] web app exception handling > > > how do you guys handle exceptions in webwork actions? > > im thinking of a situation where the db goes down and I am > unable to do anything.. how should I handle these cases? > > hows about sending them to some kind of page that says theres > an unexpected error that occured? > > > ------------------------------------------------------- > This SF.net email is sponsored by: VM Ware > With VMware you can run multiple operating systems on a > single machine. WITHOUT REBOOTING! Mix Linux / Windows / > Novell virtual machines at the same time. Free trial click > here: http://www.vmware.com/wl/offer/345/0 > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
