Hey all, One goal I had for early Turbine was that it handle uncaught Exceptions for you relatively well, hence part of the reason for the single servlet design. In other words, if one of your modules throws an exception, then a Screen should be displayed that can be customized with an error message, stack trace, whatever. Right now, we have an issue with the new Site* architecture because what happens is that when an uncaught error happens, it isn't entirely handled for you by the appropriate tool. For instance, when an error in a WebMacroSiteAction class happens, then nothing is there to display the error screen. So, I started to work on fixing this and realized it is something that I think that Dave/John Mcnally should work on fixing. The reason is that we should have some common exception handling framework for both WM and FM and whatever else we end up adding later. It also should be re-usable code across the different modules. For instance, right now, the WMSiteScreen module catches the errors, but the WMSiteAction one doesn't. Essentially, my request here is that you guys take a look at this issue and please post a proposal for designing a method to fix it. :-) Of course if you guys don't want to do it or don't have time, someone else might want to step up and look at this issue...otherwise, I will add it to my stack. :-) thanks, -jon -- http://scarab.tigris.org/ | http://noodle.tigris.org/ http://java.apache.org/ | http://java.apache.org/turbine/ http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/ http://www.collab.net/ | http://www.sourcexchange.com/ ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
