The best way that I have found to handle exceptions/errors in screens is to make sure all of your screen classes descend from one root class. You can put any kind of exception/error handling logic in the root screen class (displays, logging, admin-notification, session-invalidation, etc). Once you have done that, extract the code into a separate package, and then plug it into your Root Action class.
Chris > -----Original Message----- > From: Johnny Quazar [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 05, 2003 10:00 AM > To: Turbine Users List > Subject: suggestions to extend Turbine.handleException? > > > Hi All, > > If somebody tries to access an invalid screen, I see > Turbine.handleException takes a "java.lang.ClassNotFoundException", > should I try to extend handleException to catch this case? > > Is there any (good? easy?) way to trap all invalid screen requests? > I'll add the lame signature I use to offer my project, if somebody > drops the suffix and instead accesses: > > http://www.bitblaster.JustAnExample.com/p/s/p/template/i,Welcome > > I look really silly right out of the gate. Obviously I could alter my > error message, but I'd rather trap all invalid URL's to a specific > place. > > -- ERROR -- Turbine.handleException: > > Requested Screen not found: > Turbine looked in the following modules.packages path: > [cc.rnn.nh.modules, org.apache.turbine.flux.modules, > org.apache.turbine.mods.template, org.apache.turbine.modules] > > THANKS > > -- > Try my Homepage Toolbox! > http://www.bitblaster.com/p/s/p/template/i,Welcome.vm > > --------------------------------------------------------------------- > 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]
